[aur-general] Package orphaning policy improvement - RFC
stevenhoneyman at gmail.com
Sun May 25 11:10:50 EDT 2014
As a newcomer to packaging for the AUR, that was one of the things I
thought "I wonder why they don't do that already"
I'd read about some September cleanups (2011/2012 only?).
Also, how about if orphaned for more than 3 months, then delete?
There are some really outdated packages on there!
On 25 May 2014 16:06, Nowaker <enwukaer at gmail.com> wrote:
> Currently one has to contact the maintainer and wait 2 weeks before reaching
> a TU on the ML to take over the package. I think this is totally OK when the
> maintainer really maintains the package, e.g. has generally frequent
> updates, responds to the comments, etc.
> However, this is an overhead when it's obvious a package is no longer
> maintained. For example, those marked out-of-date for more than 3 months, or
> those that have numbers of comments requesting update with no single
> response from the maintainer.
> It includes a situation when a maintainer is otherwise active on AUR, e.g.
> they update their other packages. The fact is they don't upgrade the very
> one package that people are interested in - otherwise a package wouldn't
> have been marked out-of-date in the first place.
> What do you think about auto-orhpaning packages that stay marked out-of-date
> for more than, say, 3 months? Done automatically by AUR, with no request on
> Kind regards,
> Damian Nowak
More information about the aur-general