[MacPorts] #38010: MacPorts should prevent overlinking due to .la files
MacPorts
noreply at macports.org
Sun Feb 10 22:08:19 PST 2013
#38010: MacPorts should prevent overlinking due to .la files
-------------------------+-----------------------------
Reporter: jeremyhu@… | Owner: jmr@…
Type: defect | Status: reopened
Priority: Normal | Milestone: MacPorts Future
Component: base | Version: 2.1.3
Resolution: | Keywords: glibtool la
Port: |
-------------------------+-----------------------------
Comment (by jeremyhu@…):
Replying to [comment:22 jmr@…]:
> Defaulting to deletion right away would cause tons of breakage for the
reasons I mentioned above.
Yes, which is why I mentioned that we should have an install hook (when
installing base) that will delete any .la files that the user has
installed at the time they upgrade base.
> Sometime in the future when all the dependency_libs in installed files
are cleared, and everything that really needs them is explicitly setting
'no', then the default can change.
I fail to see how that is relevant or will help the situation. The
deployment should be:
1) Install a new base -> delete all existing .la files
2) Install new ports -> no new .la files are deployed
That's what I'm doing here, and it's working out fine. I have a couple
installs going from clean and many more doing upgrades after deleting
*.la.
--
Ticket URL: <https://trac.macports.org/ticket/38010#comment:23>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list