Mailinglist Archive: zypp-devel (149 mails)

[Peter Poeml <poeml@xxxxxxx>]

On Mon, Sep 01, 2008 at 01:45:52PM +0200, Stanislav Visnovsky wrote:
> > The problem is that the metadata creators may not be aware, or this may
> > be forgotten, or the need may arise for packages where nobody has
> > thought about it, so what I really mandate is a way to specifiy this
> > kind of configuration on the client side.
>
> True. 

Okay, we agree. Good :-)

> > If the kernels have not been marked as such so far, this only proves my
> > point, doesn't it? :)
> >
> > Also, there is no need to worry about this IMO, because if a package
> > isn't installable next to a previous version because of a file conflict,
> > the installer will tell me about it anyway, or not? And a flag in the
> > metadata doesn't fix any underlying problem.
>
> No, file conflicts are by default not caught by libzypp as the file lists are 
> not downloaded and parsed (except for specific file patterns).

This puzzles me, how does zypper deal with this? Does it detect file
conflicts only when already in the middle of installing packages?
This sounds dangerous, because it sounds as if package installation
might abort in the middle of something.

> But there is also a problem that the package might not be installable in 
> parallel even if there is no file conflict. Yes, that might be fixable by 
> black-listing instead of white-listing in metadata (the current approach).

Which problems, other than file conflicts, would that be? Could you
elaborate? 

Peter
-- 
Contact: admin@xxxxxxxxxxxx (a.k.a. ftpadmin@xxxxxxxx)
         #opensuse-mirrors on freenode.net
Info: http://en.opensuse.org/Mirror_Infrastructure
 
SUSE LINUX Products GmbH
Research & Development