1 |
this was a known issue when the ebuild made (i made it ;]) |
2 |
but the solution was to grab a stable-ish build, make the digest |
3 |
off of it, and post it to ibiblio. then, when the next stable-ish |
4 |
version came along, a new digest would be put out and the |
5 |
version be bumped up to -r1 and so on and so forth. the |
6 |
problem lays with the fact that the last release of quakeforge |
7 |
is like 0.3.0. this version is dead and majorly obsolete. |
8 |
the 'newer' versions get put out when someone famil with |
9 |
the project feels it is needed. also, that tar ball isnt auto-generated |
10 |
every single hour ... not sure if it is even autogenerated ... |
11 |
but yeah, i think the version should have had at least a |
12 |
date tag on it now that you mention it. once i fix the |
13 |
ebuild for gcc3.x ill post the new one with a date tag |
14 |
-mike |
15 |
|
16 |
----- Original Message ----- |
17 |
From: "Dan Naumov" <jago@×××××××××××.com> |
18 |
To: <gentoo-dev@g.o> |
19 |
Sent: Saturday, August 17, 2002 13:03 |
20 |
Subject: Re: [gentoo-dev] Very bad ebuild-writing practice. |
21 |
|
22 |
|
23 |
> On Sat, 17 Aug 2002 18:50:26 +0200 |
24 |
> Bart Verwilst <verwilst@g.o> wrote: |
25 |
> |
26 |
> > quakeforge-0.5.0_pre020817.ebuild |
27 |
> |
28 |
> That won't work with hourly auto-generated snapshots in the case where |
29 |
older snapshots are no longer kept on the server, just like our quakeforge |
30 |
case. This would require hourly auto-generated ebuilds and the borkage I |
31 |
mentioned in my previous mails would still exist :| |
32 |
> |
33 |
> Dan Naumov aka Jago |
34 |
> _______________________________________________ |
35 |
> gentoo-dev mailing list |
36 |
> gentoo-dev@g.o |
37 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
38 |
> |