Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

erlbrew can't install R15B03-1 because of file naming issue #8

Closed
nalundgaard opened this issue Dec 5, 2014 · 4 comments · Fixed by #9
Closed

erlbrew can't install R15B03-1 because of file naming issue #8

nalundgaard opened this issue Dec 5, 2014 · 4 comments · Fixed by #9

Comments

@nalundgaard
Copy link

When installing R15B03-1:

nal-mbpr:erlbrew nal$ erlbrew install R15B03-1
Downloading Erlang R15B03-1
######################################################################## 100.0%
Tarball has correct MD5 checksum
Unpacking Erlang R15B03-1
/Users/nal/bin/erlbrew: line 104: cd: otp_src_R15B03-1: No such file or directory

It appears that this is because otp_src_R15B03-1.tar.gz expands to otp_src_R15B03 rather than the expected otp_src_R15B03-1:

nal-mbpr:erlbrew nal$ ls .build/current
erlbrew.log             otp_src_R15B03          otp_src_R15B03-1.tar.g

I worked around this by doing this from the erlbrew directory:

## clear all work folders
rm -rf .build/work.*
## in another terminal, execute 'erlbrew install R15B03-1'
## then do this immediately:
cd /build/work.*; ln -s otp_src_R15B03 otp_src_R15B03-1
cd ../..

I am not sure what the sane thing to do about this is.

@jadeallenx
Copy link
Owner

I think we can solve this with a simple bash function which special cases R15B03-1 so that its build directory name matches the name in the tar ball. And if this comes up again in the future, we could reuse this "solution."

@nalundgaard
Copy link
Author

Yeah, that seems like a plan. More layers...

@dcgibbons
Copy link
Contributor

Or use kerl, it works really well. I've found it to work better (except for that R14 on 10.9+ issue).

@jadeallenx
Copy link
Owner

@dcgibbons Should maybe hack in a way to handle patches for kerl but its just not a priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants