On Thursday, January 30, 2003, at 07:01 pm, Max Horn wrote:
So, for now, instead of charging ahead and trying to write a new dependency engine from scratch or trying to retrofit an existing one, I went to try to write down what our needs are. Then based on this, I started to develop ideas on how to realize these needs in actual code. I try to present all my ideas and findings in this email. That includes a list of problematic cases the engine needs to handle, as well as fundamental problems, and problems that are also affecting our current system. It'll be a long email, and maybe I should put it on a web page later, too.
<snip>
Why dependency deciding is difficultA feature that would be nice to have which Fink currently does not handle dynamically, when deciding on package dependencies the engine would also consider whether to download/install any binary debs when available, and compile the rest which are not available in deb archives.
====================================
Life would be easy if a dependency would just say "install foo", and there was exactly one foo. However, foo may exist in 5
I'll also explain the chroot/fakeroot approach for package building and how it would help us in many many ways (at the cost of more time/disk space, though).This is an obvious question, but does a fakeroot jail mean duplicating files of any required dependencies into a sandbox(jail) during the build phase? So, wouldn't hard links eliminate any additional disk-space penalty?
Carsten
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
