Mailinglist Archive: zypp-devel (149 mails)
| < Previous | Next > |
Re: [zypp-devel] Re: keep kernels
- From: Stanislav Visnovsky <visnov@xxxxxxx>
- Date: Mon, 1 Sep 2008 13:45:52 +0200
- Message-id: <200809011345.53147.visnov@xxxxxxx>
Dňa Monday 01 September 2008 13:17:29 Peter Poeml ste napísal:
True.
No, file conflicts are by default not caught by libzypp as the file lists are
not downloaded and parsed (except for specific file patterns).
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).
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Mon, Sep 01, 2008 at 12:48:23PM +0200, Stanislav Visnovsky wrote:
Dňa Monday 01 September 2008 12:38:40 Michael Schroeder ste napísal:
On Mon, Sep 01, 2008 at 09:36:42AM +0200, Stanislav Visnovsky wrote:
Maybe. The behavior should be that if the package can be installed in
parallel in multiple versions, it must be marked so in the metadata.
No, that's not true.
Interesting, because above was the agreement when we discussed this. How
is it then?
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.
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).
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).
Furthermore, IMO it's more complicated than needed if it needs action on
different ends. I have been using the feature with yum for 5 years now
and I can say that the mechanism is useful in the real world in the form
implemented there.
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |