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

Fix sourcing of asdf.sh #622

Merged
merged 1 commit into from Nov 3, 2022
Merged

Fix sourcing of asdf.sh #622

merged 1 commit into from Nov 3, 2022

Conversation

cpytel
Copy link
Member

@cpytel cpytel commented Nov 3, 2022

Installing asdf via Homebrew now says:

To use asdf, add the following line to your ~/.zshrc:
  . /opt/homebrew/opt/asdf/libexec/asdf.sh

Yes, the laptop script is doing:

. /opt/homebrew/opt/asdf/asdf.sh

This used to work, but in no longer does because of the change in
Homebrew/homebrew-core#81664

This corrects the file location being source.

This failure was showing in CI and UTM locally for me.

This change also undoes the change I had made in #620. While that change did allow the error code to be seen by CI, once the fix for the actual issue was made in this branch, and asdf was able to run, I saw that the asdf.sh wasn't actually running in the context of the laptop script, and therefore asdf was not initialized successfully for the rest of the script, and the installation of ruby and node would fail.

Installing asdf via Homebrew now says:

```
To use asdf, add the following line to your ~/.zshrc:
  . /opt/homebrew/opt/asdf/libexec/asdf.sh
```

Yes, the laptop script is doing:

`. /opt/homebrew/opt/asdf/asdf.sh`

This used to work, but in no longer does because of the change in
Homebrew/homebrew-core#81664

This corrects the file location being source.

This failure was showing in CI and UTM locally for me.
@cpytel cpytel merged commit aa3a84e into main Nov 3, 2022
@cpytel cpytel deleted the libexec-asdf branch November 3, 2022 03:16
@cpytel
Copy link
Member Author

cpytel commented Nov 3, 2022

@purinkle Yes, while that change did allow the error code to be seen by CI, once the fix for the actual issue was made in this branch, and asdf was able to run, I saw that the asdf.sh wasn't actually running in the context of the laptop script, and therefore asdf was not initialized successfully for the rest of the script, and the installation of ruby and node would fail.

I've updated the PR description to make that more clear. Thanks.

eebs added a commit to eebs/dotfiles that referenced this pull request Nov 14, 2022
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 this pull request may close these issues.

None yet

1 participant