Michał Górny posted on Wed, 24 Mar 2010 12:28:38 +0100 as excerpted: > As suggested by ssuominen on bug #311101, I am posting the issue to the > mailing list. > > Currently, various SCM eclasses differ very much in the subset of > features and control variables implemented. The idea is to establish a > single subset of such variables and rules for all SCM eclasses to > follow, and maybe even develop a common scm.eclass which would be > sourced by other SCM eclasses. > > Variables suggested by me: > > a) Common variables - the variables which would have to be used by > various SCM eclasses as default/fallback values. > > 1. ESCM_DISTDIR (defaulting to PORTAGE_ACTUAL_DISTDIR/PORTDIR)
Reasonable idea... The standard note here every time source control comes up, however, is that SCM is ambiguous, conflicting with scheme (the language). VCS (version control system) seems to be the preferred alternative. I'll let the various VCS eclass using devs worry about the details... -- 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
