Mailinglist Archive: zypp-devel (227 mails)

< Previous Next >
Re: [zypp-devel] how foo-branding-myvendor can conflict with any foo-branding-*?
  • From: Stanislav Brabec <sbrabec@xxxxxxx>
  • Date: Wed, 16 Apr 2008 11:20:43 +0200
  • Message-id: <1208337643.3637.159.camel@xxxxxxxxxxxxxx>
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)

For rpm, strings will be different and file conflict will happen.

For zypp, packagefirst will create conflict, which will be ignored for
package itself and applied for all other packages.


And yet another solution I can imagine:
Do nothing. Let the error happen on rpm level.

Calling solver again after rpm level error is a planned feature.

--
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/

--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx

< Previous Next >