On Jul 11, 2013, at 3:25 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
> I suppose so. But there's still the idea of self-hosting MacPorts, where > MacPorts would come with the MacPorts port pre-installed and the selfupdate > mechanism would be just a thin shim around updating the MacPorts port: > > https://trac.macports.org/wiki/SummerOfCode#self-management It seems to me that if we're going to start making MacPorts depend on its own libraries and what not, this is the best way to do it. The "MacPorts" port could depend on "tcl", "curl", etc. > How would MacPorts itself having dependencies (on Tcl or cURL or whatever) > affect that idea? Bootstrapping from source would be weird, for one. I suppose we'd bundle Tcl with the source, install using that one, install the Tcl port, and reinstall off of the port? It sounds gross, but it would only have to happen for the initial install. (Tcl is probably the only dependency we'd have to do this with, since the bootstrap install could probably use the system libraries for everything else.) vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
