[aur-general] Package from official repos build from git, instead of official upstream release - Was: TU Application - Dustin Falgout

Eli Schwartz eschwartz93 at gmail.com
Wed Mar 2 14:28:02 UTC 2016

On 03/02/2016 07:06 AM, 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.
> [snip]

I would consider providing an official package from git only in the case
of something like trash-cli. (I maintained it in the AUR before Pierre
Neidhardt sponsored it for community.)

Upstream development is essentially dead (the developer has moved on and
doesn't really have time for trash-cli anymore), and instant segfaults
are only fixed through an unmerged pull request.
So it isn't reasonable to wait for a release, and I just pulled the
latest commit hash (via tarball) -- plus the PR.
I consider that to be the "latest version" and I was intending to update
if and when a particular new commit felt valuable.

Other projects might not do releases, just snapshots.

Bu if an active project does releases then the appropriate response is
probably as Johannes said, to backport that patch while waiting for a
stable release.

Eli Schwartz

More information about the aur-general mailing list