Package Details: ardour-git 8.0.rc1.r11.geed79f45d7-1

Git Clone URL: https://aur.archlinux.org/ardour-git.git (read-only, click to copy)
Package Base: ardour-git
Description: A multichannel hard disk recorder and digital audio workstation (git version)
Upstream URL: https://ardour.org/
Keywords: dssi ladspa lv2 mastering midi pro-audio production recorder sequencer
Licenses: GPL2
Groups: pro-audio
Conflicts: ardour
Provides: ardour, ladspa-host, lv2-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: 2023-09-25 22:13 (UTC)

Required by (112)

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 .. 21 Next › Last »

Gimmeapill commented on 2020-03-30 07:16 (UTC)

@FlyingWombat: Thanks for the heads up but I can't update right away as I don't have my arch box around (for who knows how long...). In you have an updated pkgbuild and want to step in, please send it and I'll add you as co-maintainer, that will be the fastest.

FlyingWombat commented on 2020-03-28 21:04 (UTC)

Waf has been updated; it runs on python3.

Gimmeapill commented on 2017-12-21 21:58 (UTC) (edited on 2017-12-21 21:59 (UTC) by Gimmeapill)

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

thetotalchaos commented on 2017-12-21 14:16 (UTC)

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

Gimmeapill commented on 2017-09-20 19:27 (UTC)

@speak: fixed, thanks for the heads up!

speak commented on 2017-09-20 10:42 (UTC)

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 (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.

Gimmeapill commented on 2017-08-18 10:31 (UTC)

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

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 (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.

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