Package Details: ardour-git 8.6.r406.g35cb60c2dc-1

Git Clone URL: https://aur.archlinux.org/ardour-git.git (read-only, click to copy)
Package Base: ardour-git
Description: Professional-grade digital audio workstation (git version)
Upstream URL: https://ardour.org/
Keywords: dssi ladspa lv2 mastering midi pro-audio production recorder sequencer
Licenses: MIT, CC0-1.0, GPL-3.0-or-later, GPL-2.0-or-later
Groups: pro-audio
Conflicts: ardour
Provides: ardour, ladspa-host, lv2-host, vamp-host, vst-host, vst3-host
Submitter: None
Maintainer: SpotlightKid (dvzrv, aggraef)
Last Packager: SpotlightKid
Votes: 44
Popularity: 0.000000
First Submitted: 2013-03-14 23:12 (UTC)
Last Updated: 2024-08-17 06:50 (UTC)

Required by (141)

Sources (3)

Pinned Comments

Gimmeapill commented on 2017-08-18 10:40 (UTC) (edited on 2018-02-14 11:01 (UTC) by Gimmeapill)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 21 Next › Last »

Gimmeapill commented on 2017-08-18 09:43 (UTC) (edited on 2017-08-18 09:48 (UTC) by Gimmeapill)

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 (UTC) (edited on 2017-08-18 09:25 (UTC) by Ralf_Mardorf)

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 (UTC)

@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 (UTC) (edited on 2017-08-17 06:06 (UTC) by Ralf_Mardorf)

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 (UTC) (edited on 2017-08-17 07:23 (UTC) by Gimmeapill)

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

electricprism commented on 2017-08-17 00:58 (UTC)

You might wanna change the version number to something like 5.99 if you don't want to bump it every time a 5.X release comes out. Current version is 5.11 so when I saw it in my terminal I was confused that the package version is 5.5 until coming here and confirming the PKGBUILD that it is git and not 5.5.

Gimmeapill commented on 2017-01-01 10:38 (UTC) (edited on 2017-01-01 10:39 (UTC) by Gimmeapill)

Please do not flag as out of date unless something breaks with the packaging itself. This is a git pkgbuild that always pull the latest git master branch of Ardour (which might not always build in between releases). It doesn't need to be updated with each point release. If the version is not updated properly in the package name, please make sure you are not using an AUR helper like Yaourt, and instead build with "makepkg -s".

Gimmeapill commented on 2016-11-05 10:53 (UTC)

Should be working ok now

Gimmeapill commented on 2016-10-26 20:29 (UTC) (edited on 2016-11-07 11:39 (UTC) by Gimmeapill)

Had to revert to using bundled libs, as there is no pkg in AUR for a newly introduced depdendency: qm-dsp (https://code.soundsoftware.ac.uk/projects/qm-dsp/files).

Gimmeapill commented on 2016-10-25 22:07 (UTC)

First try. Current git seems to be quite unstable though. Still some work needed with dependencies and build flags, but at least it should compile again.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 21 Next › Last »