* Xyne <xyne@archlinux.ca> [20.12.2010 23:31]:
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.
Regards, Xyne
I'm the original author of the PKGBUILD and I put it to the AUR so people who are interested can easily build it. Building the package worked quite well back then, but of course this can change a lot when it's under heavy development. Removing it would be total nonsense in my opinion, because one day ardour3 will become stable and then some people might want this package again. So why not keep it. Xyne is right in my opinion, the post_install message is a good idea. I didn't use that because I thought that those who build and use it are aware of the very early state of the development. I gave away the maintainance, because I didn't have enough time for it and right now I have to have a rock solid ardour, so I use ardour2 with jack1.