FS#7480 - Multiple versions of PKGBUILDs
Attached to Project:
AUR web interface
Opened by Dusty Phillips (Dusty) - Wednesday, 20 June 2007, 18:29 GMT
Last edited by Loui Chang (louipc) - Saturday, 14 November 2009, 04:04 GMT
Opened by Dusty Phillips (Dusty) - Wednesday, 20 June 2007, 18:29 GMT
Last edited by Loui Chang (louipc) - Saturday, 14 November 2009, 04:04 GMT
|
Details
Perhaps for AUR 2 this feature could be implemented. The
idea is that multiple PKGBUILDs for each package could be
contributed. Currently users not maintaining a package
sometimes post corrected PKGBUILDs to the comments list for
a package in the AUR. It would be neat if these could be
posted to a repository for the package and the maintainer
(not just TUs) could have the option of directly setting a
user-contributed PKGBUILD as the official one. Also, it
could give users the ability to download the revised
PKGBUILDs directly instead of copy-pasting them from the
comments. This could be useful when new versions of a
package are released and also when the maintainer
contributed package has bugs that another user has been able
to fix.
|
This task depends upon
Closed by Loui Chang (louipc)
Saturday, 14 November 2009, 04:04 GMT
Reason for closing: Won't implement
Saturday, 14 November 2009, 04:04 GMT
Reason for closing: Won't implement
Comment by
Sven-Hendrik Haase (Svenstaro) -
Wednesday, 19 August 2009, 01:43 GMT
No, this would effectively kick the whole AUR into a completely
different paradigm. Currently, each AUR entry is a definitive,
usually well maintained, package. Splitting that up further it
would use it's efficiency if you first had to decide which
PKGBUILD version to use. Your suggestion would undermine the
maintainer's duty of updating the package.
Comment by Gavin Bisesi (Daenyth) -
Wednesday, 09 September 2009, 00:07 GMT
Yeah -1 from me. If a package isn't being properly maintained, it
should be orphaned, not spread out over comments and additional
submissions. If it is being maintained, this only increases hassle
for the users.