On Mon, Dec 1, 2008 at 1:12 PM, Daenyth Blank <[EMAIL PROTECTED]> wrote: >>> In short: the community backend should really just accept packages via >>> upload (authenticated, or course), dump them in a common location >>> (/home/aur/staging) and then setup a cronjob to run db-update >>> periodically. This cronjob should also find packages in the db.tar.gz >>> and not in CVS and run db-remove on them. >>> >>> If we can collaborate enough on this, we could even use the same >>> functionality for extra and core. >> >> Note that the above regarding db-update requires a move to svn at the >> same time. I do not plan to add special code to deal with CVS >> > Regarding db-remove: I think is is an _absolute_ requirement that > packages be easily moved back to unsupported. Currently the only way > is to delete it entirely and re-upload as a new package (losing all > related metadata). It's really horrible, and I think contributes to > the glut of useless stuff in community at the moment.
Sure, but that'd be more up to the AUR front-end that controls unsupported. It'd just have to copy the entries from CVS and put them in the unsupported dir. Should be simple. As for removing them, perhaps the front-end could even remove them from CVS, but that seems a little gross.
