1 |
Alexandre Rostovtsev posted on Fri, 04 Sep 2015 10:05:31 -0400 as |
2 |
excerpted: |
3 |
|
4 |
> On Thu, 2015-09-03 at 16:00 +0200, George Shapovalov wrote: |
5 |
>> 2. Is there some standard naming scheme? Should the new eclass be |
6 |
>> called, say, |
7 |
>> gnatbuild2.eclass or gnatbuild-ng.eclass? Of course this only matters |
8 |
>> if old eclass is there to stay. If not I'll just call the transitory |
9 |
>> eclass something like gnatbuild-refactor.eclass for the duration of its |
10 |
>> existence.. |
11 |
> |
12 |
> I suggest gnatbuild-r1.eclass, that seems to be the most widely used |
13 |
> eclass versioning pattern. Some examples: |
14 |
> |
15 |
> bash-completion.eclass → bash-completion-r1.eclass (2011) |
16 |
> distutils.eclass → distutils-r1.eclass (2012) |
17 |
> emboss.eclass → emboss-r1.eclass (2015) |
18 |
> git.eclass → git-2.eclass (2011) → git-r3.eclass (2013) |
19 |
> myspell.eclass → myspell-r2.eclass (2012) |
20 |
> office-ext.eclass → office-ext-r1.eclass (2013) |
21 |
> python.eclass → python-r1.eclass (2012) |
22 |
> qt4.eclass → qt4-r2.eclass (2009) |
23 |
> |
24 |
> Other patterns: |
25 |
> |
26 |
> java-utils.eclass → java-utils-2.eclass (2006) |
27 |
> mysql.eclass → mysql-v2.eclass (2011) |
28 |
> ruby.eclass → ruby-ng.eclass (2009) |
29 |
|
30 |
Just to add... |
31 |
|
32 |
As the folks doing the git eclasses found out, bare generation numbers |
33 |
are all too easily confused with upstream version numbers -- git-2.eclass, |
34 |
is that for use with git-2*? |
35 |
|
36 |
Given that gentooers are already familiar with the -rN identifier from |
37 |
ebuilds and know that there it unambiguously indicates a gentoo revision, |
38 |
as opposed to upstream, the same idea was eventually borrowed for eclasses |
39 |
identifiers -- git-r3.eclass unambiguously indicates what git-2.eclass |
40 |
didn't, that it's the third /gentoo/ generation of git eclass, *not* just |
41 |
for /upstream/ git-v3 (when there is one). (Xref eclasses such as qt4, |
42 |
kde4, qt5... where the number indicates upstream version.) |
43 |
|
44 |
So -rN has become the standard gentoo-generation identifier for eclasses, |
45 |
meaning much the same thing as it does when used for ebuilds. If you'll |
46 |
note, the other listed patterns are from 2011 or earlier, when the |
47 |
git-2.eclass experience proved its name a confusing mistake and |
48 |
effectively catalyzed the standardization around the -rN pattern that |
49 |
was apparently (based on the above dates) first used with qt4-r2.eclass |
50 |
in 2009. |
51 |
|
52 |
-- |
53 |
Duncan - List replies preferred. No HTML msgs. |
54 |
"Every nonfree program has a lord, a master -- |
55 |
and if you use the program, he is your master." Richard Stallman |