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