I'm really talking about two things, one of which is no problem. 1. being able to change compile time options
No problem, its already possible. Everyone agrees that you better know roughly what you're doing, or the package won't work. 2. being able to dynamically find & satisfy dependencies Definitely a challenge, hasn't been solved yet. If you put 1 & 2 together, then you have a software system that is highly customizable & yet easy to use. In fact, Fink already partially does 2 -- every time it asks the user to choose between different ways of satisfying some dependency. But I'm saying (as a class project or something) - throw an Expert System into Fink that will be able to map you from compile time options to dependencies, automatically (again leaving the user the choice as to how to satisfy a dependency when there's an overlap). ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
