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 non-default PKG_CONFIG_PATH on macOS #503

Merged
merged 1 commit into from
Apr 15, 2019

Conversation

alyssais
Copy link
Contributor

PKG_CONFIG_PATH shouldn't be reset, only appended to or prepended to, so that the user can still use non-default paths if they need to. Additionally, package managers other than Homebrew (such as Nix) still need to be able to provide their own versions of packages, and aren't going to use Homebrew's default path to do so.

PKG_CONFIG_PATH shouldn't be reset, only appended to or prepended to, so
that the user can still use non-default paths if they need to.
Additionally, package managers other than Homebrew (such as Nix) still
need to be able to provide their own versions of packages, and aren't
going to use Homebrew's default path to do so.

Signed-off-by: Alyssa Ross <hi@alyssa.is>
@msbit
Copy link
Contributor

msbit commented Apr 14, 2019

@GPaulovics, this fixes unintended consequences from the previous PKG_CONFIG_PATH fix I put in for macOS, and the issue will be hurting the Nix folks (as @alyssais mentioned) so it might be worth trying to get this released.

@GPaulovics GPaulovics merged commit d1eba80 into lastpass:master Apr 15, 2019
@GPaulovics
Copy link
Contributor

@alyssais @msbit I just created a release specifically for this, and it is currently under review on brew as well. Sorry for taking this long.

@alyssais alyssais deleted the pkg_config_path branch July 8, 2019 11:57
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

3 participants