Le 17/12/2012 16:32, Richard Heck a écrit :
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?
The problem is that we cannot \usepackage 50 different packages in a
same latex instance without and expect that there will be no conflict.
It is not doable IMO.
In moderncv, I see:
\ProvidesClass{moderncv}[2008/06/17 v0.7 modern curriculum vitae
document class]
The version is not relevant, since LaTeX identification is based on
dates. This date should be easy enough to grep out for most classes, but
I suspect some cases will require us to do explicit code.
[However, read below]
While looking into moderncv.cls, I saw an interesting line:
\RequirePackageWithOptions{moderncvcompatibility}
Looking inside this file is indeed interesting:
% compatibility with version 0.1
\newcommand*{\cvresume}[2]{\cvlistdoubleitem{#1}{#2}}
% compatibility with versions <= 0.2
% section, cvline, ... with width argument...
%\newcommand*{\section}[2][0.825]{%
% \closesection{}%
[...]
So, Uwe, are you sure that you the problem you fixed is real? It seems
that the moderncv author did his homework and that he takes backward
compatibility seriously. Do we really need to update the layout file
every release???
I wonder whether the problem we are trying to solve is real.
JMarc
