[aur-general] Package from official repos build from git, instead of official upstream release - Was: TU Application - Dustin Falgout
johannes at kyriasis.com
Wed Mar 2 12:23:01 UTC 2016
On 02/03, Ralf Mardorf wrote:
>On Wed, 2 Mar 2016 12:28:58 +0100, Levente Polyak wrote:
>>> The simplest way to make these "static" if you want to import them
>>> into [community] is to pin the git source using #commit=1234567.
>>Also in that case, only if you have a sane reason to not stick to the
>>upstream released versions. If there is no real reason one should
>>follow the upstream released version so the commit hash should not be
>>arbitrary but the one of the release.
>>In general we want to follow upstream releases.
>Would this [A] be a reason to provide an official package from git?
>If so, I'll report a request to build jack2 from git.
> Date: Wed, 24 Feb 2016 00:38:22 +0100
> From: Robin Gareus
> To: ardour-users at lists.ardour.org
> Subject: Re: [Ardour-Users] Export hangs after script executing
> 1.9.11 (actually git: 1.9.10-g1ed50c92) is known to be good WRT to this
> freewheeling bug.
That's more of a reason to backport the fix rather than getting all
unreleased commits in the package. Or get them to make a new release.
PGP Key ID: 0x50FB9B273A9D0BB5
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1768 bytes
Desc: not available
More information about the aur-general