Re: Strange buildconflicts
Jeffrey Johnson <[email protected]> Mon, 26 Aug 2013 13:27:49 -0400
| Newsgroups | gmane.linux.mandrake.cooker.devel |
|---|---|
| Message-ID | <CEFAE74E-E882-4AC8-B1F0-E9905E73149D__18547.0894015909$1377538088$gmane$org@me.com> |
On Aug 26, 2013, at 1:17 PM, Per =D8yvind Karlsen wrote: > When touching db* packages, I notice this odd buildconflicts: > BuildConflicts: libreoffice-core >=20 While I have no idea what the semantic intent of the above is/was, I can = point out BuildObsoletes: exists/functions and is perhaps a better solution than = BuildConflicts: if the intent is to create a tree in which a package can be rebuilt. = Note that the effect is harmless when installing as non-root (which is suggested as best = practice for rpmbuild for many years now), but would permit re-running "sudo = rpmbuild" and "fixing" the problem automagically. Note also that BuildRequires: !libpreoffice-core (note the leading ! for negation) is essentially the same as the = BuildConflicts: used. There is a similar symmetry relationship between BuildObsoletes: and = negated BuildProvides:, the major difference being the actual side-effect when a negated = dependency is evaluated against the complement of the installed set. (if that statement doesn't make sense, Don't worry! Be Happy! Let's go = shopping!) hth 73 de Jeff