I know this has gone around before... but, to flog a dead horse a bit more because this has really started to be a serious hindrance to Fink in the eyes of many people I know.We don't generally accept bundled .apps in fink, because they can be moved by the user, and also to keep fink focused.
1) There is no reason for Fink to install apps in /Applications. Applications work fine anywhere on the disk. So do frameworks.
2) Apps can't be moved any more readily than, say, /sw/bin/python or /sw/share/doc/apache. Same goes for frameworks.
3) More and more Unix related tools have native Aqua ports available. tk and wx immediately come to mind. Film-gimp on the applications front. With PyObjC, CamelBones, and other bridge type technologies coming along, I'm sure there will be more. Many of these require or, at the least, are designed to use an app wrapper.
I don't see how supporting the *native* version of something like tk or wx would be a loss of focus for Fink. If anything, it tightens the focus -- it continues the fine tradition of Fink providing highly tuned, ultra-compatible, builds of Unix/Open Source projects to the OS X community.
Besides-- it seems really sad that FinkCommander isn't a standard part of the Fink installation....
b.bum
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel