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

Improve package prefix selection on FreeBSD #552

Merged
merged 2 commits into from
Apr 21, 2020

Conversation

oxc
Copy link
Contributor

@oxc oxc commented Nov 4, 2019

On FreeBSD, the package prefix is currently hardcoded to php56. This change modifies the default behaviour to use the prefix matching the selected php version (from globals) if defined.

This change should be fully compatible, since the default is to fallback to php56, and if a custom version is specified, the package prefix has to be manually configured to match this version anyway.

Futhermore, the pear package is now using a php prefix as well (since 2018-03-08), which is also fixed by this pull request.

@ghoneycutt
Copy link
Member

Tests would help this get merged or someone else verifying this works with FreeBSD 9-11.

@bastelfreak bastelfreak added enhancement New feature or request needs-rebase labels Apr 19, 2020
@bastelfreak
Copy link
Member

@oxc please rebase against our latest master branch.

oxc added 2 commits April 21, 2020 09:56
As of 2018-03-08, pear is flavored/prefixed in FreeBSD[1]. Remove the
special handling and use the configured prefix as for most other
distributions.

[1] See UPDATING note e.g. on https://www.freshports.org/devel/pear/
If the php version has been set in globals, use it to determine the
default package prefix on FreeBSD.
This should be a compatible change, since the package prefix can still
be overridden, and has to match the selected version anyway.
@oxc
Copy link
Contributor Author

oxc commented Apr 21, 2020

@oxc please rebase against our latest master branch.

Done.

@bastelfreak bastelfreak merged commit 80e9279 into voxpupuli:master Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants