| Summary: | Add PHP 7.1 framework | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Torsten Zuehlsdorff <tz> | ||||
| Component: | Ports Framework | Assignee: | Port Management Team <portmgr> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Only Me | CC: | gasol.wu, ports-bugs | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Torsten Zuehlsdorff
2017-01-04 10:55:07 UTC
Mmmm, if the aim is to ask for an exp-run, please submit the full patch. > Mmmm, if the aim is to ask for an exp-run, please submit the full patch.
Sorry, i should have make myself more clear:
The aim is to get approval (or somebody doing it) to commit this needed part of the patch to Mk/. After that i can commit this rest of the patch (or all in once)
As far as i understood the policy changes to Mk/ need approval of portmgr@, or am i wrong?
Most files in Mk have MAINTAINER defined somewhere, you have to get approval from them. For bsd.default-versions.mk, ports@ so no approval. For Uses/php.mk, it is supposed to be ale. What portmgr wants to have a looksie at, and possibly run tests is infrastructure changes, to make sure it works, but even if we sometime rewrite everything, we don't maintain all of it :-) Changes were already done and PHP 7.1 moved into the ports-tree :) |