#28865: p5-libwww-perl: new version 6.01, which is now in multiple modules distributed separately ------------------------------+--------------------------------------------- Reporter: l2g@… | Owner: l2g@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: p5-libwww-perl ------------------------------+--------------------------------------------- Changes (by l2g@…): * owner: narf_tm@… => l2g@… Comment: I need a little advice on this. Since there will be multiple ports containing the same files as the current p5-libwww-perl port contains, there is a catch-22 when upgrading. MacPorts starts upgrading p5-libwww- perl, then sees the new dependencies. So it tries to bring in the dependencies first. As soon as it hits a port with files overlapping the original p5-libwww-perl, there's a file conflict and the upgrade halts with an error. This can be worked around by deactivating p5-libwww-perl first, but how best to tell the admin to do that? Or is there a better way to handle something like this? -- Ticket URL: <https://trac.macports.org/ticket/28865#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS