Re: update-all

Alexander Hansen <[email protected]>
Newsgroups gmane.os.apple.fink.core
Organization Fink Core Team
Message-ID <[email protected]>
On 5/4/12 2:38 AM, Guillaume Ponchel 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.
> 
> The only workaround I found in this situation is to manually update
> the later packages before going back to the previous one. This is why
> I venture to ask you if it might be an improvement to automatically
> skip the package with error and try the next. At the end of the (first
> cycle of the) updating-process, the failed updates could then be
> retried.
> 
> With best regards,
> 
> Guillaume Ponchel.
> 


If a package truly needs a particular version of a dependency, it is
supposed to indicate that in its description, and that isn't the fault
of "update-all".

If, on the other hand, you're talking about a situation where you start
with e.g. libgettext3-dev and a package wants libgettext8-dev, i.e.
where the two versions are considered to be separate packages, then this
can indeed be a problem.

However, I believe it would be quite difficult to modify fink to move on
from a failed build attempt in a batch build.  "fink update-all" is
basically the same operation as "fink install <package>"; in the latter
case we don't want fink to move on if a dependency fails.

You can accomplish the same thing with a little shell scripting, though:

for pkg in `fink list -it | cut -f2` ; do fink -y update $pkg ; done

It's a little inefficient:

1) fink may try to install packages that have already been installed as
dependencies for something else, but it will quickly move on to the next
package in such a case.
2) fink will scan for updated packages on every operation rather than
just once.

But it works.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/2012/02/21/got-job/

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
fink-core mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.core
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-core
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.