FS#17625 - <makeconflicts> , Could it be useful?

Attached to Project: Pacman
Opened by Nezmer (Nezmer) - Sunday, 27 December 2009, 20:39 GMT
Last edited by Allan McRae (Allan) - Tuesday, 30 March 2010, 03:26 GMT
Task Type General Gripe
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

So we have <depends>, <makedepends>, <conflicts>, <provides> and <replaces>.
What about <makeconflicts> ?

I faced a corner case today that could have benefited from such a feature.

gstreamer0.10-bad-plugins needs schroedinger to support proper dirac decoding. schroedinger depends now on orc(Oil Runtime Compiler). A gstreamer plugin named cog uses orc internally and conflicts with the stand-alone compiler.

What that means?
If you try to build gstreamer0.10-bad{,-plugins} using the official PKGBUILD and with schroedinger and orc installed, the build will simply fail.

Luckily, with this corner case I simply added "--disable-cog" to ./configure and had my schroedinger,dirac plugins properly built. But the process made me think about <makeconflicts>.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 30 March 2010, 03:26 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See comment. A note in the PKGBUILD would be the best approach.
Comment by Allan McRae (Allan) - Monday, 28 December 2009, 22:01 GMT
My initial impression is that this would always be an incomplete list and that a note inside the PKGBUILD would be better.
Comment by Gavin Bisesi (Daenyth) - Wednesday, 17 March 2010, 04:33 GMT
I don't think this is worthwhile. Best not to let the feeping creatures attack.

Loading...