AUR web interface

Tasklist

FS#2257 - TUR individual repositories

Attached to Project: AUR web interface
Opened by Link Dupont (link) - Wednesday, 23 February 2005, 07:26 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Not sure if this is planned or not, but I do find it helpful to have my "own" repository for putting packages that aren't really stable or decent enough for "staging" (or AUR); for example, my helixplayer & realplayer packages. There may be licensing issues with realplayer, and so I'd prefer to keep it out of the official channels until any issues have been resolved. My own TUR is a great place for that.
This task depends upon

Closed by  Paul Mattal (paul)
Monday, 07 March 2005, 04:03 GMT
Reason for closing:  Not a bug
Comment by Ben Mazer (contrasutra) - Wednesday, 23 February 2005, 22:00 GMT
I think this would get too convoluted. The purpose of the AUR is to house "official" packages only -- ones that would be ready for inclusion in EXTRA or CURRENT.

I think you should just leave whatever package it is in UNSUPPORTED.
Comment by Eric Johnson (eric) - Saturday, 05 March 2005, 20:13 GMT
I'll second Ben's comment. Anyone can run a personal repo and put whatever they want in it. "Unsupported" is the place for users to upload PKGBUILDs they would like to see enter more official channels. If it's well packaged and popular, it will go probably be adopted by a TU and put into the AUR. From there, if it is popular enough, it will go into extra/current.

Any beta/CVS snapshot/devel type packages should not be submitted to Unsupported/AUR, IMO.
Comment by Link Dupont (link) - Sunday, 06 March 2005, 17:05 GMT
I see your point, and will concede my argument. You may close this if you wish. :)

Loading...