Package Details: ardour-git 6.0.pre0.r38.ga42f6ff828-1

Git Clone URL: https://aur.archlinux.org/ardour-git.git (read-only)
Package Base: ardour-git
Description: A multichannel hard disk recorder and digital audio workstation
Upstream URL: http://ardour.org/
Keywords: dssi ladspa lv2 mastering midi production recorder sequencer
Licenses: GPL
Conflicts: ardour
Provides: ardour
Submitter: Boohbah
Maintainer: Gimmeapill
Last Packager: Gimmeapill
Votes: 40
Popularity: 0.048781
First Submitted: 2013-03-14 23:12
Last Updated: 2017-09-20 19:25

Required by (2)

Sources (2)

Pinned Comments

Gimmeapill commented on 2017-08-18 10:40

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.

If you are looking for the latest official release instead, see
https://aur.archlinux.org/packages/ardour_stable-git/

Latest Comments

Gimmeapill commented on 2017-09-20 19:27

@speak: fixed, thanks for the heads up!

speak commented on 2017-09-20 10:42

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.

Gimmeapill commented on 2017-08-18 10:40

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.

If you are looking for the latest official release instead, see
https://aur.archlinux.org/packages/ardour_stable-git/

Gimmeapill commented on 2017-08-18 10:31

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

Ralf_Mardorf commented on 2017-08-18 09:59

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 ;).

Gimmeapill commented on 2017-08-18 09:43

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.

Ralf_Mardorf commented on 2017-08-18 08:58

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.

Gimmeapill commented on 2017-08-17 21:10

@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/

Ralf_Mardorf commented on 2017-08-17 05:54

Hi electricprism,

you seem not to understand the git related policy. FWIW if you want 5.11, instead of the latest commit from git, you anyway need to edit the PKGBUILD:

"$ man PKGBUILD | grep " fragment" -A6
fragment
(optional) Allows specifying a revision number or branch for makepkg to checkout from the VCS. For example, to checkout a given revision, the source line would have the format source=(url#revision=123). The available fragments depends on the VCS being used:

[snip]

git
branch, commit, tag"

However, I recommend first to do, what I usually prefer to do, to e.g. build Ardour 5.10 I run

asp checkout ardour

edited the PKGBUILD's pkgver and 'SKIP' the checksum, before running

makepkg -s

this is what I'll do today or within the next days for Ardour 5.11, too. It might be that additional changes are required, but since on LAU it was announced that it "is primarily a bug-fix release", it much likely builds without issues without additional editing.

Gimmeapill already explained that this PKGBUILD is only out of date, if it is broken. The release version shown is completely irrelevant for git related PKGBUILDs.

Btw. yaourt updates versions properly when using git PKGBUILDs. The only pitfall I'm aware of is, that by default it builds in /tmp which usually is tmpfs, so the RAM might be to small to build bloated software. Assuming

df -h

should show 3.9G or more for /tmp, Ardour should build, it even might require less space, if not

yaourt --tmp /a_non-tmpfs_dir <aur_package_name>

should do the trick.

Regards,
Ralf

Gimmeapill commented on 2017-08-17 05:21

@electricprism: This is a git package, it doesn't have any hardcoded version number and always pulls the latest development snapshot.
The package version is retrieved from the source via a function and follows the packaging guidelines.

See:
https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function

If you want only stable releases, better use the official package (although it seems to be lagging a bit at the moment).

All comments