Best way to handle sub-package conflicts

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

 



Hi all,

  I am creating a new RPM package for a cluster project we've created.
There is a common "core" package, and then three other packages that are
installed depending on the machine's role in the cluster;

foo-core
foo-A
foo-B
foo-C

  If 'foo-A' is installed, I want 'foo-B' and 'foo-C' to be removed, and
'foo-B' replaces 'foo-A' and 'foo-C', etc. I originally planned to use
'Conflicts: ' in our spec, but reading this:

https://fedoraproject.org/wiki/Packaging:Conflicts

  It seems like 'Conflicts' is strongly discouraged. So instead I tried
'Obsoletes', and this seemed to work in that, if 'foo-A' was installed
and I tried to install 'foo-B', it would remove 'foo-A'. So I thought I
was ok, until I bumped the version and tried to to an update. With
'foo-A' installed, it wanted to install 'foo-B' and 'foo-C' and failed,
which makes sense now that I think of it.

  What is the best way to handle this in the .spec file? I'm having
trouble finding the right term to search form.

Thanks!

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux