I think this is true for at least parent, as I explained before I have many users ask where a pkg is, like in the case of mplayer which depends on libavcodec which is in ffmpeg. Fink will say it can't find the depend on libavcodec, and then ppl don't know where to find this. Now if it's not in there tree this won't help but I figured the PDB might be able to use it at least and other then that it's a good devel tool as would fink locate so you know what file it's reading from, which I wanna add next but i wanna wwait to see if you are gonna add a devel space first.

---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 9-Dec-03, at 1:53 PM, Max Horn wrote:

I wonder why you think so? Why would a non-developer need these? All situations I can think off were they might need it are scenarios were they have to fix/workaround bugs. I.e. it's like with tools to repair a car: the average car driver should never have to use them, but some people still want to be able to use them, and sometimes the car is not well built so you prefer learning how to repair it yourself instead of having to pay for the service (i.e. "ask on a mailing list") each time. But that's more a sign of a not well made car (i.e. it means there are things in fink which should be improved).

It's the "cure of the symptom" vs. "cure of the cause" debate. IMHO you shouldn't have to know about splitoffs at all, if you have to, then usually because you need to cure a symptom, but the real fix would be for the fink developers to cure the cause :-)


Just to clarify something: When I say I consider these as "developer commands", that doesn't mean I want to prevent "normal" users from using them. Rather it means that the primary audience for them will be fink developers/packagers. Just like Apple's Developer Tools: Everybody can install them, but most non-developers have no reason. Of course there are still some non-developers (e.g. Fink users :-) who may want to install them anyway, which is fine.

Attachment: PGP.sig
Description: This is a digitally signed message part



Reply via email to