On Dec 31, 2003, at 1:21 PM, Ben Hines wrote:
I have been thinking about this some more, and I would now like to propose this seriously as a solution for several problems that were biting us recently. The more I think about it, the more it seems to me that we will *have to* do this.
Here is the proposal:
1. Allow the packages that have "BuildDependsOnly: true" (short: "buildonly" packages) to Depend on other buildonly packages
2. Introduce a "reaper" that removes *all* buildonly packages. The reaper has to run every time before fink starts a package build process.
Doesn't sound like a good idea. Many people (including me) who actually use fink packages for development would be very unhappy about this. I need a lot of our buildonly packages (e.g. -dev package with header files). Having to manually reinstall them whenever I use fink to install something would be a nightmare (and essentially make fink useless).
You wouldn't, dude. It'd be optional and you'd be able to hold certain packages of course. These are obvious problems which I immediately considered. I am also a developer/
Oops, clicked send to early.. anyway, obviously such a mechanism would have to keep track of what packages the user told fink to install, and which were simply installed as a blind build dependency. Again, obvious issues. It is absolutely a great idea to get these unnecessary packages off people's systems who do not want them while keeping them for people who do.
-Ben
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
