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

[Kurt Hindenburg]

Hello,
   A few ideas if they haven't been mentioned:
- Check all local sources (sources.conf)
     - If there are Portfiles in sub-folder, if PortIndex exists
     - If the system port has a newer version
     - Any duplicate ports in multiple local sources
- Multiple $PATH entries in shell startup files

Regards,
    Kurt

On 7/21/14, 5:33 PM, Kyle Sammons 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
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140722/c5b25d07/attachment-0001.html>