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.
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.
FS#20833 - Move all PKGBUILD.proto to the pacman repository
Attached to Project:
Pacman
Opened by David Campbell (Davekong) - Monday, 13 September 2010, 00:23 GMT
Last edited by Allan McRae (Allan) - Wednesday, 06 October 2010, 14:11 GMT
Opened by David Campbell (Davekong) - Monday, 13 September 2010, 00:23 GMT
Last edited by Allan McRae (Allan) - Wednesday, 06 October 2010, 14:11 GMT
|
DetailsAll of the PKGBUILD.proto's should be part of the pacman repository. The code in makepkg directly relates the SCM PKGBUILDs, it is confusing having some of the prototypes in one repository and others in another, and it means that they are less likely to get updated at the same time.
|
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 06 October 2010, 14:11 GMT
Reason for closing: Won't implement
Additional comments about closing: See comments
Wednesday, 06 October 2010, 14:11 GMT
Reason for closing: Won't implement
Additional comments about closing: See comments
Should this be just the SCM prototypes or the ruby/haskell/perl/gnome etc prototypes too?
But that is the advantage that pushed me to -1. e.g. abs-3.4.0 was released on Saturday and 3.4.1 will be release this week with an added python prototype (among other things). With pacman, adding a prototype could take six months to a year.
Of course, if the prototypes in ABS fall behind again, send a patch and I will push an update.