Summary: | Mk/bsd.php5.mk: Regression: mod_php5 is out of the dependency tree when WANT_PHP_WEB is set | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Melvyn Sopacua <m.r.sopacua> |
Component: | Ports Framework | Assignee: | Alex Dupre <ale> |
Status: | Closed Works As Intended | ||
Severity: | Affects Many People | ||
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Melvyn Sopacua
2014-08-05 03:11:52 UTC
Not sure who to assign this to, let's try ale@ first. If you are using the port system the dependency will be added, since it will look at the installed SAPIs. Packages are different, you should expect inconsistencies if you change default OPTIONS. Anyway, what the port system does is more than it should, I could completely remove such tricky check and let all ports depends on core php and stop. (In reply to Alex Dupre from comment #2) > If you are using the port system the dependency will be added, since it will > look at the installed SAPIs. I installed it in a clean system using the ports. The results posted are what the package has recorded, but they were still being installed. I changed the options simply to trigger a mod_php5 build, since WANT_PHP_WEB is supposed to pull in a web-capable SAPI or bail out with a fatal error. Neither happened. So this means it's not working as intended. > Anyway, what the port system > does is more than it should, I could completely remove such tricky check and > let all ports depends on core php and stop. I actually think that's best. With mod_php5 out of the main php5 port, it becomes impossible to maintain a WANT_PHP_WEB semantic that works reliably. Instead, depending ports should be fixed to offer support for the SAPIs they want to support. At present I maintain at least one port that wants both a CLI and a web sapi, and I'm more then happy to change the options and add PHP SAPI selection and help to fix others as well. |