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)
signature.asc
Description: This is a digitally signed message part
