Am Mittwoch den, 20. Mdrz 2002, um 01:44, schrieb Ben Hines:
Actually, it is fairly easy to make modifications to Fink's .info
files to suit your tastes, add compiler flags, whatever. Remove
the tcl dependency and make a "system-tcl" package that points at
your OS install.
Well, instead of patching the Fink system, I'd rather patch the
originals :-) Fink is just too closed a system for my taste, but
this is just *my taste*, so no need to argue...
But if you really don't want to bother, you can use fink's info
and patch files as cheat sheets that show you how to get the thing
building.
Maybe I don't know the system well enough, but this wasn't helpful
in my case.
And as previously mentioned, patches are always submitted
upstream. The comment about "stabilizing the gap" is baseless.
The author of the Fink website explicitely states that he considers
submitting patches a lower priority he doesn't always have time
for. Therefore my impression.
Putting stuff in its own domain is pretty smart when you realize
that apple can and will write over whatever UNIX-layer stuff it
wants (WITHOUT asking) when you install OS updates.
Apple will certainly not touch /usr/local (or else! ;-)) ). The
problem of Fink seems to be the dependence of various packages on
one another. If you have a single package that compiles against a
"pure" OS X, I see no problem at all to install it into
/usr/local - that's what /usr/local is for!
Uli Zappe email@hidden
Lorscher Stra_e 5 http://www.ritual.org
D-60489 Frankfurt Fon: +49-700-ULIZAPPE
Germany Fax: +49-700-ZAPPEFAX
________________________________________________________
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
