Alternate package implementation (how can I provide and conflict with the same package?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I would like to put an alternate implementation of a package into my
repository and be able to switch it in and out of use.

Lets say there is a standard package "foo" and I want to swap it out for
my own package "myfoo", but be able to swap back the original package
with ease.

If I say my package both provides "foo" and obsoletes "foo" I can
switch from "foo" to "myfoo" just fine.  My new "myfoo" package can be
installed replacing "foo".  But switching back is not as easy as
installing "foo" since "foo" is now obsolete.

I would like to have each package obsolete the other when it is
installed.

I have control over "myfoo" since I build it myself, but the "foo"
package is provided by another.

I want to replace one package with the other, but be able to switch
back with ease.

The alternatives (UPDATE-ALTERNATIVES(8)) system seems like a
nightmare of symlinks.  Not exactly what I'm after.

Playing tricks with version numbers seemed like a bad idea also.

I'm told this can be done with aptitude on Debian.

How would I do it with RPM / Yum?

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux