#47808: port:jpeg proposal to prepare for making port:libjpeg-turbo the default jpeg dependency --------------------------+-------------------------- Reporter: rjvbertin@… | Owner: ryandesign@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: jpeg | --------------------------+-------------------------- Comment (by rjvbertin@…): Or more in general, if `path:libjpeg.dylib:jpeg` is resolved by any port other than port:jpeg, the dependency is still registered as being on port:jpeg. At least that's what I was told when I asked about this a while back, and we agree that's an oversight at least. The fact that a path: style dependency also allows to resolve a dependency with a binary that doesn't come from a port at all is iffy too (but sometimes comes in handy O:-) ). Replacing a dependency by something ABI compatible post-installation is a different issue. I don't know if one could expect the registry to be rewritten in that case. After installation of a port, information about its dependencies is used only to prevent uninstallation of the dependencies (and to keep track of ports gone useless), right? With accepted practice I referred to using a path: style dependency to provide a choice between a regular port and its -devel "variant". -- Ticket URL: <https://trac.macports.org/ticket/47808#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X