[aur-general] ttf-google-webfonts{,-distilled,-git,-hg} mess

[Daniel Micay]

On Thu, Apr 25, 2013 at 3:10 PM, David J. Haines <djhaines at gmx.com> wrote:
> On Thu, Apr 25, 2013 at 01:01:37PM -0400, Daniel Micay wrote:
>> On Thu, Apr 25, 2013 at 12:35 PM, Mateusz Loskot <mateusz at loskot.net> wrote:
>> > On 25 April 2013 17:15, Maxime GAUDUIN <alucryd at gmail.com> wrote:
>> >> On Thu, Apr 25, 2013 at 5:31 PM, David J. Haines <djhaines at gmx.com> wrote:
>> >>> On Thu, Apr 25, 2013 at 11:17:36AM -0400, Jonathan Arnold wrote:
>> >>> > On Thu, 25 Apr 2013 16:04:12 +0100
>> >>> > WorMzy Tykashi <wormzy.tykashi at gmail.com> wrote:
>> >>> >
>> >>> > > > So, then the solution is for the -git maintainer to update /
>> >>> > > > re-upload the PKGBUILD whenever there's a "version" bump to the git
>> >>> > > > repo?
>> >>> > > >
>> >>> > >
>> >>> > > No, the solution is for the users of the -git package to track
>> >>> > > upstream changes and re-compile the package as and when they see fit.
>> >>> >
>> >>> > As it is for all -git (and -svn and -hg, etc) packages. As it should
>> >>> > be, IMHO.
>> >>> >
>> >>>
>> >>> Thus the utility of the -tarball PKGBUILD: users don't have to track it;
>> >>> they can rely on the maintainer.
>> >
>> >>
>> >> Such a thing is only true when using AUR helpers, which, again, are not
>> >> supported. Even as a helper user, I don't think the -tarball package is
>> >> needed.
>> >
>> > As user of AUR, I agree.
>> > I'm slowly getting sick of the AUR mess and spread of duplicate packages
>> > motivated by some narrow corner cases and customisation.
>> > Either makepkg and PKGBUILD is enhanced to properly support the development
>> > kind of packages, namely *-{git|hg|svn} and perform actual update of
>> > local copy of sources
>> > (even if PKGBUILD has not been updated)
>> > or users have to accept the fact they play with cutting-edge version of software
>> > so they take care of updates it on their own.
>> >
>> > Stop AUR insanity!
>> >
>> > Best regards,
>> > --
>> > Mateusz Loskot, http://mateusz.loskot.net
>>
>> makepkg has full support for VCS packages now, it runs the pkgver
>> function to check for a new version and then updates/rebuilds. It even
>> knows how to fetch the sources automatically.
>
> Well until PKGBUILD and the AUR report versions correctly, I'd want to
> see the -tarball variant (and others like it) stick around. That's my
> two cents.
> --
> David J. Haines
> djhaines at gmx.com

A tarball does not have the version reported any more correctly. The
AUR reports the version set as pkgver which is just set when the
maintainer builds the package and re-uploads, if there's a pkgver
function. There's no relevance of a tarball vs. VCS when it comes to
the reported pkgver.