Am Sonntag, 20.07.03 um 07:41 Uhr schrieb Kyle Moffett:
I would like to propose a new internal engine for fink, based around an Objective C library that I will call Finch in this email. I will be unavailable for the next 3 weeks, but will work on code in my spare time. When I get back, I will send a link to whatever I come up with. Here is my proposal:Just one word "conflict handling". The single most biggest problem. Plain forward dependencies are trtivial to handle and are already handled in the existing engine. The hard cases are conflicts, and the many many border cases, e.g. when upgrading stuff. But maybe it's best you try it out to see what I am talking about, maybe that's more convincing than me explaining it for the 100,000th time.
Firstly, I believe that the solution to many of the build-depends, multi-threading, etc issues revolves around a simplistic reference engine. Each package maintains a list of references with reference types (For example: bar-2.6.5 = ["foo-2.3.4-2", "Required"],["USER","Requested"]) Then only when all references are destroyed is the package removed. Similarly, it could use the same list for opposing references, depending on the state of the install flag.
Anyway, I fail to see the point in your desire to rewrite everything from scratch. But we'll see if you actually have an even partially useable prototype in 3 weeks, much better to discuss *that* than any vaporware :-)
Max
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
