[aur-general] Moving packages to Community

Gergely Imreh imrehg at gmail.com
Sat Feb 5 13:31:43 EST 2011


Recently a couple of my packages have been moved to Community but the
process feels a little uneasy to me.

My impression is that AUR is treated as a "second class" source of
packages compared to the official repos. Not surprising, of course, so
many packages have problems. This is also underlined by the fact that
yaourt and other AUR managers are not allowed in the official repos,
as "not to give the impression that AUR is official" (paraphrasing
what I've read before).

If there is indeed this divide, it feels more than little weird, that
popular packages are just taken in to Community without even asking
the current managers. It gives me the message that "AUR has no value,
except when we say it has, at which time thanks for your work but now
bugger off". I beg your pardon, if it comes through too harsh. I
wouldn't have objected to have those packages moved. I, however,
object to unilateral decisions.

My proposition is: could it be a policy to check with the maintainer
first before initiating a move? If someone wants to keep a package
then they should be able to, especially since they could not have been
doing such a a bad job if their package has become popular.


More information about the aur-general mailing list