On Mon, Jul 6, 2009 at 13:59, Stefan Husmann<stefan-husmann@t-online.de> wrote:
I think the easiest way to archieve something similar to point one is to encourage everyone who orphans a package to leave a short comment, i.e "orphaning", on AURs comment page. Everyone who gets notifications about that package (and these are the candidates for adoption) will get a mail then, and no code changes are needed.
Regards Stefan
Right, but why tell users to perform a two manual actions (orphan, comment) in order to trigger an automatic action (notification) when the notification can be triggered automatically by the action of orphaning it. It would require a code change, but I can't imagine it's a large one. The largest hassle is probably that of translating the message.
I think this is the best solution. Perhaps an AUR account for Phrik could be created and then used to insert comments automatically when a package is orphaned. With such a system in place, maybe we could implement a "replaced" function for deleting packages. For example, when a project moves from cvs to git, to delete foo-cvs you would hit replace then enter foo-git. A comment from Phrik would state the package has been replaced by foo-git and then after a fixed amount of time (a month?), foo-cvs would be autopruned. This could be added to the JSON output too to make it easier to track name-changing updates.