Arch Linux User Repository

This package will automatically retrieve and build the latest development snapshot of Ardour from git.

It does not need to be updated on every release, so please do not flag out of date unless the build breaks.

@thetotalchaos: not 100% sure but this might work if you install locally, so change the following lines:

...

conflicts=()

...

python2 waf configure --prefix=/usr/local \

--configdir=/etc/local \

...

"${pkgdir}/usr/local/share/applications/ardour.desktop"

Gimmeapill Can you hint me, how to change the pkgbuild, so that i can use this alongside the official version? ThaNKS

@speak: fixed, thanks for the heads up!

Hi! I noticed a problem with how this package is built: The line:
--with-backends="jack,alsa,dummy " \

Should be:
--with-backends=jack,alsa,dummy \

Currently the session tools don't get built properly, because the "dummy" backend isn't properly detected by the build scripts, because of the extra space inside the quotes.

This package will automatically retrieve and build the latest development snapshot of Ardour from git.

It does not need to be updated on every release, so please do not flag out of date unless the build breaks.

Good idea, thanks. The scope difference between the two packages should be explained as clearly as possible.

My apologies, I was mistaken, so your frankenword makes sense :D. The problem then is, that users next time want to build ardour_stable-git 5.12 and will flag the package out-of-date. Consider to add a pinned comment to ardour_stable-git ;).

Well, as long as the official package is not updated regularly, it does make sense to have a git pkgbuild that automatically builds the latest release without having to worry about versioning (and that is less experimental than the latest development snapshot).

"asp checkout ardour" is a nice replacement for abs, but at the time of writing it would still build 5.9, or you have to edit the pkgbuild manually (ok, not a big deal but since this can be automated, why not...)

The point of ardour_stable-git is: with just a "makepkg -s", to download the latest git commit, then to figure out what is the latest released version from the tags, set the version variable from that info, then rollback the local repo to that tag and build it. No further manual intervention. But yeah - that's not a method described in the packaging standards.

Regarding "$pkgname-$pkgver::git+https://github.com/${pkgname^}/$pkgname.git#tag=$pkgver"
-> that doesn't work because the package version is not known at the time the git repo is cloned.
The only way I found to retrieve the latest release tag without downloading would be to use git ls-remote but then the parsing is sketchy at best. So it needs to download first...

Otherwise, yes, there are not too many differences with the official pkgbuild, that's intentional. The only thing that's tied to 5.X is actually the desktop shortcut - I'll probably fix that eventually. The build flags would probably deserve a review as well.

Hi, ardour_stable-git is well-intentioned, but makes no sense. Checkout the PKGBUILD from official repositories.
asp checkout ardour
cat ardour/trunk/PKGBUILD
The probably better way:
"$pkgname-$pkgver::git+https://github.com/${pkgname^}/$pkgname.git#tag=$pkgver"
The only difference you provide is building the dummy backend. If we build ardour from the asp chekcout and Ray should update ardour, a pacman update could automatically recognise it. "stable-git" is a nice frankenword, but if you want to provide a package with an appropriate name, use "ardour5". "ardour5" was already provided by the AUR, perhaps you need to adopt this deleted package.

@Ralf_Mardorf: I get your point. The ardour developement snapshots are indeed a pain to deal with for productive use. But editing manually the pkgbuild is also a pain ;-)

So I tried to get the best of both worlds and made a new pkgbuild that builds the latest stable release and nothing more.
It's a dirty kludge that clones the latest snapshot, finds the latest release tags, then rolls back the local repository to that version and builds it.
There's probably a better way to do it, but it seems to work and the versioning shouldn't need any update until 6.x:

https://aur.archlinux.org/packages/ardour_stable-git/