On Thu, Apr 25, 2013 at 10:07:16AM -0400, Daniel Micay wrote: > On Thu, Apr 25, 2013 at 9:24 AM, David J. Haines <[email protected]> wrote: > > On Wed, Apr 24, 2013 at 10:32:36PM -0400, Daniel Micay wrote: > >> On Wed, Apr 24, 2013 at 10:28 PM, Jason St. John <[email protected]> > >> wrote: > >> > On Sun, Apr 7, 2013 at 5:11 PM, Maxime GAUDUIN <[email protected]> wrote: > >> >> On Sun, Apr 7, 2013 at 10:55 PM, Marcel Korpel > >> >> <[email protected]>wrote: > >> >> > >> >>> On Tue, Apr 2, 2013 at 12:59 AM, Maxime GAUDUIN <[email protected]> > >> >>> wrote: > >> >>> > I mostly agree with you, but I would still keep the git package > >> >>> > because > >> >>> I, > >> >>> > and I believe most people, don't want to pull 2Gb from the mercurial > >> >>> > repo > >> >>> > and keep them lying around. This is painfully slow and, even though > >> >>> > 2Gb > >> >>> are > >> >>> > nothing today, it is silly to waste space like this. The git repo > >> >>> contains > >> >>> > only the relevant TTF files and I think it is the better choice for > >> >>> > whom > >> >>> > wants to download the Google web fonts. > >> >>> > > >> >>> > How do others feel about this? > >> >>> > >> >>> I totally agree with this. > >> >>> > >> >>> Regards, > >> >>> Marcel > >> >>> > >> >> > >> >> Okay, the only remaining webfonts packages in AUR are now > >> >> ttf-google-webfonts-git and ttf-google-webfonts-hg. > >> >> > >> >> Cheers. > >> >> -- > >> >> Maxime > >> > > >> > I noticed that a new package named ttf-google-webfonts-tarball [1] was > >> > uploaded yesterday. > >> > > >> > The submitter of the package states, "This is for all those who use > >> > simple AUR helpers, e.g. cower, that need a version number to know > >> > that there's been an update and/or those who don't like the git/hg > >> > repos just hanging around on their systems (i.e. those who delete > >> > their AUR sources and packages)." > >> > > >> > Do the TUs feel that this package is necessary? It suffers from the > >> > same problem of frequent and endless maintenance that > >> > ttf-google-webfonts did that I mentioned in my first email in this > >> > thread. > >> > > >> > [1] https://aur.archlinux.org/packages/ttf-google-webfonts-tarball/ > >> > > >> > Jason > >> > >> I don't feel like this is at all necessary. The AUR helper part is > >> definitely a non-issue because bumping the pkgver on a VCS package > >> with a proper pkgver function works just fine. > > > > I created it for those of us who need it. If you use yaourt (which many > > a TU would attempt to dissuade you from doing), it may work, but for > > others of us, it does not. No one's asking you to use it, but it should > > be an option, IMHO. > > > > As to the "AUR helper part [being] definitely a non-issue," that's > > demonstrably wrong. Either ttf-google-webfonts-git's PKGBUILD suffers > > from a lack of "a proper pkgver function," or something more than such a > > function is required for certain AUR helpers to recognize that an update > > is needed, as the April 14 updates to the repo were not enough for cower > > to pick up on the new version. A review of the source code makes it > > clear that at least certain AUR helpers will not be able to handle the > > pkgver function route as currently implemented. > > > > -- > > David J. Haines > > [email protected] > > The version on the tarball PKGBUILD is updating when you upload a new > one. The version on the VCS package is uploading when the maintainer > re-uploads it. It's not relevant to whether a tarball package is > useful.
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? -- David J. Haines [email protected]
