On 21 December 2010 06:30, Xyne <xyne@archlinux.ca> wrote:
I don't agree with him. Any real archer will want to use a PKGBUILD to do this. Removing it from the AUR will just force people to recreate the same PKGBUILD themselves and for no good reason. Admittedly the AUR in combination with the various AUR helpers makes it easy for a casual user to install the package, but I don't think there will be a wave of disinterested users installing the package. Plus those very same AUR helpers make it trivial to quickly update to the latest version with a single command.
I recommend leaving it on the AUR while making it *very* clear that it is strictly for development and testing, and that users should subscribe to the upstream mailing list.
You could do this by including very visible instructions in the post_install message (along with a once-off post_update message to inform existing users).
This is only my opinion though. I'm interested in the other TUs' views.
I used to warn and advise against uploading any kind of buildscript for ardour3. I believe I was wrong. I believe the biggest headache a PKGBUILD solves is dependencies. So +1 this stays with post-install messages.