mod_* & libtool

[Bjarne D Mathiesen]

Lawrence Velázquez wrote:
> On Jun 3, 2012, at 10:28 p.m., Bjarne D Mathiesen wrote:
> 
>> If macports is able to install the macports tcl as the first port,
>> doesn't that solve the problem ???
>>
>> And I do realise that macports has to be able to be installed using the
>> resources available from the stock OS, but once it /is/ /installed/ we
>> ought to be able to bring whatever we need for any port into the system
>> - incl a newer version of tcl
> 
> So MacPorts base itself would require the tcl port right from the get-go? Even if I have no intention whatsoever of using it? What would happen if I tried to uninstall it?

MacPorts base _would_ require it _if_and_only_if_ any port requires the
added/expanded functionalty comming with the newer version of tcl. In
that case, I can see no conflict with what we already do : install
dependencies on eg Perl. In any case, I regard installing the macports
tcl just as a completely normal and in no way any different from a
normal dependency

If you force un-install the macports tcl, installing ports that require
the macports tcl during installation will still function as they should
in daily use. If, however, you've force un-installed the macports tcl
it'll be re-installed when you re-install, new-install, upgrade any port
that requires the macports tcl during the installation. Otherwise, you
can just remove it again without any problems. macports ports that
_don't_ require the added functionality found in the macports tcl will
continue to function fully as usual during installation & running.

The port command in itself _without_ the macports tcl installed will
still function fully as usual with no degraded functionality at all as
it's only dependent on the Apple tcl.

-- 
Bjarne D Mathiesen
København N ; Danmark ; Europa
----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3