From: D. M. <dm...@ne...> - 2012-05-04 16:06:41
|
On Fri, 4 May 2012 11:38:15 +0200, Guillaume Ponchel <gui...@gm...> wrote: Dear Fink devellopers, > > after a prolonged periode without update (several weeks) the list of > packages (and dependencies) to update might be quite long. This is why > the update-all command has been develloped. > > However, (1) the update-all-process progresses through the list of > package to update alphabetically (am I wrong ?) and (2) to be updated, > some packages might need a later one in the list to be already > up-to-date. So, when this situation appears, the updating process is > stoped, as a fatal error is reported. There are some mistakes/confusions in the technical details there. Just like with a simple "fink update SOMEPACKAGE", fink's engine reads the dependencies of SOMEPACKAGE and builds/installs those first (recursively for the dependencies of those dependencies, etc.). If you "fink update PKG1 PKG2" (or "fink update-all", which is just an automatically constructed list of PKG1 PKG2 etc), it will do the dependencies for each in the correct order for the dependency chains. The only time fink chooses alphabetical order is if there is no dependency chain to follow that would establish some other order to follow. dan -- Daniel Macks dm...@ne... |