What would YOU like to see 'port doctor' do?

Eric Gallager egall at gwmail.gwu.edu
Wed Jul 23 08:13:19 PDT 2014

On Tue, Jul 22, 2014 at 2:28 AM, Joshua Root <jmr at macports.org> wrote:

> On 2014-7-22 10:08 , Adam Dershowitz wrote:
> > A few ideas:
> > Checking for files that should not be in macports directory, that end up
> being there.  They could be left either by an old install, or by a
> different installer that inappropriately put them in the directory (there
> was some recent discussion of an installer for an application that was
> built using macports then shipped with an installer so the installer would
> just put stuff there).  Perhaps this could be done by looking at all the
> files in /opt/local and comparing with all the port contents?  Any extras
> are an error.
> Unfortunately this is not quite that easy, as there will be various
> config files, data files, cache files and so on that are not registered
> to a port.
Besides those, there are also the files installed by base itself:
and also the symlinks created by `port select`:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140723/e43ab677/attachment.html>

More information about the macports-dev mailing list