On 12/17/2012 04:57 AM, Jean-Marc Lasgouttes wrote:
Le 16/12/2012 19:33, Richard Heck a écrit :
Let me address the last point first. I do not see why you think
versioning makes more work. Why would you have to write three different
layouts? To support every single version of moderncv? We don't do that
now, as you said. Why would we have to do it then? Are you worried that,
if a layout is tied to a version thus:
version=0.15
then somehow it stops working when the version changes? We can mark
layouts as
version=0.15-
and then if we release a new version after a couple releases, we can
change the old one to:
version=0.15-0.19
with the new version now being:
version=0.20-
collaborate with others who are using different versions, too.
Just a technical point: I am not sure that it will be so easy to get
the file version in configure.py. It is of course doable, but I fear
we have to resort to hand-written grep patterns for some layouts.
How does LaTeX figure out the version, if we include that in
\usepackage? Or is that the worry, that not all classes do it the same way?
I was kind of thinking that we'd actually make this check in
chkconfig.ltx. Perhaps using something like:
\usepackage[version]{pkgtotest}
and then see if we actually got it? I guess maybe that's harder (or
impossible) for classes?
rh
