Date: Fri, 03 Jul 2020 12:00:46 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246915] [NEW PORT] audio/ardour6: Multichannel digital audio workstation (6.x) Message-ID: <bug-246915-7788-EGVMjAmclP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246915-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-246915-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246915 --- Comment #10 from Michael Beer <beerml@sigma6audio.de> --- (In reply to daniel.engberg.lists from comment #9) The link the ardour project provides points always to the current version o= nly. The reason why you can't just take a release (tagged version) from github is more complicated. I hope, I explain it correctly:=20 The C++ file 'revision.cc' is not checked in on the git server but is creat= ed on the fly by the used build system (waf) with the help of git. This works perfect if actually work on a cloned repository and build ardour= .=20 However this would also mean that you need to have the complete '.git' fold= er available. For a freebsd port this would mean to include the entire .git to= the pkg-plist file, which is certainly not desired to have. There is this 'release' mechanism in github which builds a tar ball. This however doesn't support this particular version feature. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246915-7788-EGVMjAmclP>