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
Task Type Feature Request
Category General
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 3.4.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

All 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
Comment by Allan McRae (Allan) - Monday, 13 September 2010, 02:04 GMT
I did intend to make a new ABS release to reflect the changes in PKGBUILD prototypes with pacman-3.4.0 but have been sidetracked. But this sounds a reasonable idea.

Should this be just the SCM prototypes or the ruby/haskell/perl/gnome etc prototypes too?

Comment by David Campbell (Davekong) - Monday, 13 September 2010, 02:22 GMT
All of them. If they were part of pacman, I am guessing they would have been updated with the changes to makepkg that warrented updates and released at the same time.
Comment by Allan McRae (Allan) - Tuesday, 05 October 2010, 05:27 GMT
@Dan: opinion on this? I'm +/-0.
Comment by Dan McGee (toofishes) - Tuesday, 05 October 2010, 15:00 GMT
I'm the same. I see the benefits as David mentioned, but it also has the drawback of being a lot slower moving in the pacman package- the abs package can be quickly updated and things added/removed without the necessary steps of a pacman release.
Comment by Allan McRae (Allan) - Tuesday, 05 October 2010, 22:01 GMT
Yeah... ABS releases can be made rather quickly, but the maintainer is a lazy bastard... :)

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.
Comment by Allan McRae (Allan) - Wednesday, 06 October 2010, 14:11 GMT
I have decided to "Won't Implement" this. I think we can reconsider added the VCS prototypes once the makepkg VCS packaging overhaul happens, but the GNOME/ruby/perl/... etc maybe too distro specific for inclusion in makepkg anyway.

Of course, if the prototypes in ABS fall behind again, send a patch and I will push an update.

Loading...