Ryan Schmidt wrote: > On second thought, I don't see why we want to install MacPorts using > MacPorts. Doesn't that make it impossible to install MacPorts if you > do not already have MacPorts?
No, I think MacPorts would need to do some bootstrapping on install. But it would make commands like this answer correctly: $ port provides /opt/local/bin/port Additionally, ports could maybe require a specific version of MacPorts later (given a new dependency engine capable of this). So an upgrade of base could be delayed until it is absolutely necessary. Currently, the installation is not easily capable of removing files from existing installations on upgrade. We need to manually remove paths we no longer use in 'make install' and the postflight script (for example I did so for the old non-compressed man pages). Rainer _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users