1 |
On Sat, Aug 17, 2002 at 07:09:05PM +0300, Dan Naumov wrote: |
2 |
> I've just found something that I personally consider very bad ebuild-writing practice and filled a bug-report about it at: http://bugs.gentoo.org/show_bug.cgi?id=6642 I also think, it's worth pointing out to some who don't visit BugZilla, as I consider the issue to be rather important: |
3 |
> |
4 |
> ================================= |
5 |
> app-games/quakeforge/quakeforge-0.5.0.ebuild claims to provide the users with a 0.5.0 release. The 0.5.0 release does NOT even exist. The only thing that exists is a 0.5 development branch, from which, a 0.5.0 release will be eventually made. |
6 |
> |
7 |
> SRC_URI="http://www.quakeforge.org/files/quakeforge-current.tar.bz2" points to a CVS snapshot that's autogenerated every hour without going through any kind of QA. Since when do we allow ebuilds to point at hourly CVS snapshots of a development tree of a program that is undergoing heavy changes ?! If you emerge quakeforge using that ebuild, it might refuse to compile because the tree is broken at that very moment. It might compile, but the compile options have changed making the ebuild somewhat obsolete. And even if it compiles, it *WILL* break, because it's expected of it, it's a development tree. |
8 |
> |
9 |
> Bad. Bad. Bad. |
10 |
> ================================= |
11 |
> |
12 |
> Sincerely, |
13 |
> Dan Naumov aka Jago |
14 |
> |
15 |
|
16 |
I understand how the case above is misleading in that most people |
17 |
expect a relatively stable release using that naming convention. |
18 |
|
19 |
But suppose someone did want an ebuild for the hourly CVS snapshots? |
20 |
How should it be named? |
21 |
|
22 |
quakeforge-0.5.0.ebuild # works, but is misleading |
23 |
quakeforge-0.5.0-cvs.ebuild # ERR! |
24 |
quakeforge-0.5.0_cvs.ebuild # ERR! |
25 |
quakeforge-0.5.0_cvs_hourly.ebuild # ERR! |
26 |
quakeforge-0.5.0_beta1.ebuild # OK, but misleading also |
27 |
??? |
28 |
|
29 |
I have made a few ebuilds and one thing that frustrates me is |
30 |
the very particular ebuild naming requirements. In fact, I have |
31 |
an ebuild pending in which I had to use a version number of |
32 |
zero even though there is no version yet in order to get it to |
33 |
work. |
34 |
|
35 |
http://bugs.gentoo.org/show_bug.cgi?id=6209 |
36 |
|
37 |
-- |
38 |
Jeremiah Mahler |
39 |
<jmahler@×××××××.net> |