[aur-dev] Moving packages to Community

Martti Kühne mysatyre at gmail.com
Mon Feb 7 12:11:21 EST 2011

Hello official and inofficial maintainers and AUR devs.

Following the discussion in aur-general, I think some automation could
solve many issues at once here. Justin Davis' community-blacklist
patch is an approach in about the right direction.... although in
relation to the discussion concerning these prevailing [more-official
repo] adoption issues, it seems that it does not yet go far enough at
the moment. There should be a redirection or at least a
[we're-now-official] error page showing sort of "congratulations and
sorry for the late notice" to the yet uninformed aur maintainer, if
his package is not reachable any more because it was adopted in said
[more-official repo] - along with this could be displayed the comments
of the former package. As well, it could just become invisible in the
package's search, and marked with a "I saw this" button in the former
AUR maintainer's package list. When that button is clicked, the
package would sink quietly into the official repo without anyone
needing to complain.

The only hurdle remaining is, that a package isn't up for deletion any
more when it gets adopted to [more-official repo], because that could
just be automated by the repo's backend maybe? I'm probably going to
download the aur source inclusively Justin's approach to look into
this a bit further. Even though my development skills aren't exactly
in line with such a task, and if someone feels more confident, one may
look into it h{im,er}self.

I'd like to hear your comments on this well.


More information about the aur-dev mailing list