Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#15918 - '*' in PKGBUILD for the conflicts array

Attached to Project: Pacman
Opened by Attila (attila) - Wednesday, 12 August 2009, 14:24 GMT
Last edited by Dan McGee (toofishes) - Friday, 14 August 2009, 01:59 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

Since there starts a new splitting game with the kde/kdemod packages i have little wish for own packages. Would it be possible at example to use this

conflicts=("kdebase-*")

if i want to use a variation of the kdebase package which is build for personal use in one package.
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 14 August 2009, 01:59 GMT
Reason for closing:  Won't fix
Comment by Dan McGee (toofishes) - Wednesday, 12 August 2009, 17:33 GMT
I'm not a big fan of this. The idea of conflicts is you know ahead of time the exact packages you wish to conflict with. This could end up being overzealous in conflict resolution down the road.
Comment by Attila (attila) - Thursday, 13 August 2009, 05:02 GMT
You have right that the risk is very big to you ruin your package database but i speak only from 'private use' where i risk only my system. My goal is that i don't wnat to control every time the big list of the splitted PKG's from one kde package. If there would be a better solution than fine and i can understand why you don't like this.
Comment by Allan McRae (Allan) - Thursday, 13 August 2009, 05:04 GMT
I do not think this is possible _in general_ at the packaging stage (makepkg). It would have to be a feature in pacman to expand the conflicts.

I do agree with Dan that this could have unexpected consequences due to excess conflict resolution. But that would be a packaging issue. I think we can revisit whether we want to do this after FS#1561 is implemented.

BTW, this appears to work at first glance... conflicts=$(pacman -Ssq kdebase-)
Comment by Attila (attila) - Thursday, 13 August 2009, 18:00 GMT
@Allan Nice idea. For me this is enough because this will even presents the current list without looking for a new split package. And because this is my first goal, for me this feature request can be closed. Thanks for your time.

Loading...