Yeah, I've actually currently built against the MacPorts Tcl. I don't recommend it, but it was the easiest way to rebuild between developer seeds. I kind of like the idea Ryan was talking about where we build using a portfile or something, and then squirrel the files away someplace away from the main install.
—Mark _______________________ Mark E. Anderson <e...@emer.net> On Mon, Jul 8, 2013 at 2:32 PM, Daniel J. Luke <dl...@geeklair.net> wrote: > On Jul 7, 2013, at 11:00 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > In fact, just naively making MacPorts base link with libraries provided > by MacPorts ports would be brittle and unwise, e.g. if MacPorts base used a > library from MacPorts cURL, and the user deactivated MacPorts cURL, then > MacPorts wouldn't be able to use cURL anymore. But as I said it's possibly > worth looking into ways of solving it. > > > indeed, back a /long/ time ago I had built MacPorts against MacPorts > provided tcl and then forgotten and uninstalled MacPorts tcl (it was an > interesting situation to recover from) ;-) > > -- > Daniel J. Luke > +========================================================+ > | *---------------- dl...@geeklair.net ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > >
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
