=?ISO-8859-1?Q?=22D=2E_H=F6hn=22?= <[EMAIL PROTECTED]> wrote: > Daniel Macks wrote: <snip> > | But it seems like there's an underlying problem with > | "Essential: yes" of fink-mirrors not being respected? > | > Well, what I noticed is, that fink-mirrors is installed _after_ the new > fink is executed. I guess, that it is problematic when the new fink > tries to download an updated, essential package _before_ fink mirrors > gets installed. Is there a way to bundle the install of fink-mirrors and > fink _before_ executing the new fink ?
But the user should still have the old version of fink-mirrors installed, and when the new fink re-executes it should find that one. And the old version should have been able to resolve the mirror (even with a not quite up-to-date list of mirrors). So I am just as puzzled as Dan about what is going on. And I agree with him, that as a backup (only to be used if the mirror list is not found) we should have a "default" value for each of our mirror types. -- Dave ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
