FS#24318 - libpipeline has no reason to be in base group

Attached to Project: Arch Linux
Opened by Taylan Ulrich B. (taylanub) - Tuesday, 17 May 2011, 11:12 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 18 May 2011, 16:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Dependencies of base packages don't have to be in the base group themselves.
libpipeline doesn't seem to me like a package you would explicitly put in the base system.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 18 May 2011, 16:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in trunk next build.
Comment by Taylan Ulrich B. (taylanub) - Tuesday, 17 May 2011, 21:32 GMT
  • Field changed: Percent Complete (100% → 0%)
Are all dependencies of all packages in the base group also in the base group?
If man-db depends on libpipeline, it will list it as a dependancy in its package metadata (which it already does); there is no need to add libpipeline to the base group.
Comment by Ionut Biru (wonder) - Tuesday, 17 May 2011, 21:33 GMT
@Andy, i don't see any reasons to have this in base group.

Loading...