> I'm Making a DepEngine.pm Max, I suggested this approach to Justin the other day.
step 1: clearly define the interface to the dependency engine, in terms of some functions that can be called, and what arguments must be passed to those functions (and what will be returned) step 2: restructure the current Engine.pm to define and call those functions (just a refactoring of current code) step 3: do development work on a new DepEngine.pm module which will reimplement those functions, presumably adding new features like build/conflicts and/or shlibs. DepEngine.pm will export functions of the same names and same syntax, so that once everything has been tested, it can be a "drop-in replacement" for the same functions in Engine.pm. By doing things this way, Justin can do his development work in cvs HEAD, without disturbing the main line of development until his new engine routines are thorouoghly tested. -- Dave ------------------------------------------------------- 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
