[aur-general] Moving packages to Community
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. cheers! mar77i
Not that I wouldn't mind the credit but it was Lukas Fleischer who implemented the official repo checking code and not me. He is also hosting the git repository for his branch of the AUR. Your idea sort of sounds like "retiring" a package to me. That seems like an interesting idea but I am not sure the benefits are worth the work involved. The benefits that I can see are: + keeping a backup of the source package (for whom? are they that valuable?) + keeping a backup of the comments, which hardly anyone can see (the original author? TUs?) Just to be specific, a TU clicks the "Retire" button on a package to retire it. A retired package is hidden from the general user. Only the original author can see it. I suppose TU or devs could see it as well, in a special swanky section of the site. Problems I brainstormed: - what happens if the original author disowns his invisible retired package? does he lose it never to found again? would anyone care? - what sort of design on the web could be used to show old retired package comments? you can't hide a package and show its comments. who is the end-user for old musty comments anyways? Anyways there you go. If I were the one expected to spend time programming this (for free) I would say that it's not worth the effort. -- -Justin
participants (2)
-
Justin Davis
-
Martti Kühne