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

[Adam Dershowitz]

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.
A check for a mismatch between the installed system version  and the system that was present for port installs (to catch upgrades that were not done correctly)

--Adam

On Jul 21, 2014 5:33 PM, Kyle Sammons <ksammons at macports.org> wrote:
>
> Hey everyone,
>
> I've been working on a command, "port doctor" that checks for common issues in the user's environment. I've implemented just about everything I, Michael D, Snc, and Neverpanic can think of, so I was wondering if you guys had anything else you'd like to see check by doctor. Currently, doctor checks for:
>
> - Errors in $PATH
> - Incorrect Xcode version
> - Curl and Rsync being installed
> - MacPorts residing in the correct location (/opt/local)
> - Amount of disk space remaining
> - X11.app being installed on OS X 10.6
> - Dylibs in /usr/local/lib
> - Header files in /usr/local/include
> - All archives from installed ports being on disk
> - All files installed by ports being on disk
> - Fink being installed
> - Homebrew being installed
> - Compilation error, "couldn't create cache file"
> - The script /Developer/Library/uninstall-developer-folder not being run.
>
> If you guys can think of anything else that should be implemented, I'd be more than happy to do it! 
>
> Thanks,
> Kyle
>
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner, and is 
> believed to be clean.