Re: [gentoo-dev] Very bad ebuild-writing practice.

["mike" <vapier@netzero.com>]

this was a known issue when the ebuild made (i made it ;])
but the solution was to grab a stable-ish build, make the digest
off of it, and post it to ibiblio.  then, when the next stable-ish
version came along, a new digest would be put out and the
version be bumped up to -r1 and so on and so forth.  the
problem lays with the fact that the last release of quakeforge
is like 0.3.0.  this version is dead and majorly obsolete.
the 'newer' versions get put out when someone famil with
the project feels it is needed.  also, that tar ball isnt auto-generated
every single hour ... not sure if it is even autogenerated ...
but yeah, i think the version should have had at least a
date tag on it now that you mention it.  once i fix the
ebuild for gcc3.x ill post the new one with a date tag
-mike

----- Original Message -----
From: "Dan Naumov" <jago@telefragged.com>
To: <gentoo-dev@gentoo.org>
Sent: Saturday, August 17, 2002 13:03
Subject: Re: [gentoo-dev] Very bad ebuild-writing practice.


> On Sat, 17 Aug 2002 18:50:26 +0200
> Bart Verwilst <verwilst@gentoo.org> wrote:
>
> > quakeforge-0.5.0_pre020817.ebuild
>
> That won't work with hourly auto-generated snapshots in the case where
older snapshots are no longer kept on the server, just like our quakeforge
case. This would require hourly auto-generated ebuilds and the borkage I
mentioned in my previous mails would still exist :|
>
> Dan Naumov aka Jago
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>