Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2763 - package types (classes?)
Attached to Project:
Arch Linux
Opened by Aaron Griffin (phrakture) - Tuesday, 24 May 2005, 18:03 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 27 July 2005, 09:19 GMT
Opened by Aaron Griffin (phrakture) - Tuesday, 24 May 2005, 18:03 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 27 July 2005, 09:19 GMT
|
DetailsSo, I thought about this a bit... I think arch would benefit greatly from having a defined set of "package types". It should be fairly open-ended, but would remove alot of repetative code.
for instance: pkgtype=module would run depmod -ae upon install pkgtype=scrollkeeper would run the whole mess of scrollkeeper updates pkgtype=fonts would update all the needed font stuff these types should reference scripts to do the duties... to make everything concise, I'd say including the scripts in the package would be a good idea (that is, only the packager needs the scripts locally) with something like this, it would be fairly easy to only upgrade the kernel when all pkgtype=module packages are likewise updated I could see a feature like this being a very good step for pacman (and packagers), however, it may be complicated to implement |
This task depends upon
Closed by Judd Vinet (judd)
Monday, 28 November 2005, 19:04 GMT
Reason for closing: Duplicate
Additional comments about closing: See #1588
Monday, 28 November 2005, 19:04 GMT
Reason for closing: Duplicate
Additional comments about closing: See #1588