Hey There, I've packaged 11 packages upto now and the reason why I don't choose to use the Maintainer tag but the Contributor tag is that AUR Packaging Standards says: When building packages for Arch Linux, you should adhere to the package guidelines below, especially if you would like to contribute your new package to Arch Linux. as the first sentence. The word "contribute" is in bold which always made me think that I'm not maintaining the package but I'm contributing the distro. Hope this helps to understand a user point of view. Cheers.. Alper KANAT <alperkanat@raptiye.org> Abhishek Dasgupta yazmış:
Many packages in Arch don't have Maintainer tags in their PKGBUILDs (around 345 last time I checked). Also quite a few the PKGBUILDs are not updated by the current maintainer.
It is better to do away with maintainer tags altogether, since their functionality can be obtained from the web interface itself.
Another alternative which I prefer (and which was discussed a while back) is to elevate the maintainer tag to a proper *required* tag which would be parsed by the Django frontend to update the maintainer list.