On Tue, Jul 22, 2014 at 2:28 AM, Joshua Root <j...@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: https://trac.macports.org/ticket/37853 and also the symlinks created by `port select`: https://trac.macports.org/ticket/43996
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
