Mailinglist Archive: zypp-devel (227 mails)

< Previous Next >
Re: [zypp-devel] how foo-branding-myvendor can conflict with any foo-branding-*?
  • From: Michael Schroeder <mls@xxxxxxx>
  • Date: Wed, 16 Apr 2008 11:41:39 +0200
  • Message-id: <20080416094139.GA31377@xxxxxxx>
On Wed, Apr 16, 2008 at 11:20:43AM +0200, Stanislav Brabec wrote:
Stephan Kulow wrote:
Am Dienstag 15 April 2008 schrieb Klaus Kaempf:
(from libredcarpet:rc-queue-item.c)
/* Check to see if we conflict with ourself and don't create
* an uninstall item for it if we do. This is Debian's way of
* saying that one and only one package with this provide may
* exist on the system at a time.
*/

Does sat-solver get this right ?
Does it matter to rpm only solutions?

I can imagine any ugly way to hide self conflict to rpm:

Conflicts: packagefirst(name_of_the_package:string_used_as_a_hash)

For example:
Conflicts: packagefirst(gimp-branding:branding-openSUSE)

What is "packagefirst"? How about:

Provides: bootsplash-branding
Conflicts: otherproviders(bootsplash-branding)

Or something like that.

Cheers,
Michael.

--
Michael Schroeder mls@xxxxxxx
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups