On 20 March 2013 17:45, Rashif Ray Rahman <schiv@archlinux.org> wrote:
Anyway, ardour3 will just roll in as ardour with a version bump, while the existing ardour will be relegated to an ardour2 package
I take that back. Ardour 2.x bugs will not be given much priority, according to the lead developer: "you can file them, but i'm not likely to fix them unless they are (a) relatively simple to fix (b) not addressed by changes in 3.x (c) serious" So it doesn't qualify to remain as a package. Will "drop" an 'ardour2' to AUR, unless someone else wants to maintain it in [extra] or [community]. If you do, be ready for the caveats. Presently, it doesn't build against latest lilv due to a change in a function return type. This is fixed in git upstream but the change is not easy to backport (I've tried but failed), and upstream will not help in this case. You _could_ package a git clone, but why the trouble? :) -- GPG/PGP ID: C0711BF1