Bug 199406
| Summary: | Adjust UNIQUENAME to also include PKGNAMESUFFIX | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Gerald Pfeifer <gerald> | ||||
| Component: | Ports Framework | Assignee: | Port Management Team <portmgr> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Some People | CC: | bdrewery, dbn, ports-bugs, sunpoet | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
This would need a few additions, a UNIQUENAME_OLD that's what it was if different, and some compat shims to move/copy the options in UNIQUENAME_OLD to UNIQUENAME so that people don't loose their options. *** Bug 183372 has been marked as a duplicate of this bug. *** UNIQUENAME has been depreciated. |
Created attachment 155529 [details] Proposed patch This is related to a discussion we had after I converted the lang/gcc* ports to use a PORTNAME of just "gcc" and have PKGNAMESUFFIX indicate the specific version. That worked just fine -- except it broke the logic around USE_LDCONFIG which relies on UNIQUENAME, where it turned out those names really were not unique any more after my "simplifications". Right now UNIQUENAME does include PKGNAMEPREFIX, but not PKGNAMESUFFIX. On the mailing lists there was consensus to change that, and I am attaching the straightforward patch to do so.