[latex3-commits] [git/LaTeX3-latex3-xcolor] main: README date to match package (f927b2f)

David Carlisle d.p.carlisle at gmail.com
Thu Sep 30 09:40:45 CEST 2021


On Wed, 29 Sept 2021 at 23:20, Frank Mittelbach
<frank.mittelbach at latex-project.org> wrote:
>
> Am 29.09.21 um 23:25 schrieb David Carlisle:
> > Repository : https://github.com/latex3/xcolor
> > On branch  : main
> > Link       : https://github.com/latex3/xcolor/commit/f927b2ff675678e03f5e9e2e173baa22816911cc
> >
> >> ---------------------------------------------------------------
> >
> > commit f927b2ff675678e03f5e9e2e173baa22816911cc
> > Author: David Carlisle <d.p.carlisle at gmail.com>
> > Date:   Wed Sep 29 22:25:14 2021 +0100
> >
> >      README date to match package
> >
> >
> >> ---------------------------------------------------------------
> >
> > f927b2ff675678e03f5e9e2e173baa22816911cc
> >   README | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/README b/README
> > index c81492b..f57d060 100644
> > --- a/README
> > +++ b/README
> > @@ -1,7 +1,7 @@
> >   Package `xcolor' by Dr. Uwe Kern
> > -(xcolor at ukern dot de)
> > +Maintained by the LaTeX Project https://github.com/latex3/xcolor/issues
> >
> > -v2.12 (2016/05/11)
> > +v2.13 (2016/09/21)
>
> I would take this out ... or replace it with a generic reference. These
> days the CTAN folks always want the stuff to match up and that usually
> goes wrong. Point to the xcolor.pdf for version number  or just drop it
>
> frank

Yes I was thinking that l3build tag could keep the version numbers in
sync as we do in some other repos, I didn't add the necessary update
function yet as I first I need to get l3build to build the ctan
distribution which needs a custom lua typeset function as the ctan
release includes xcolor2.pdf which is extracted from the main dtx  but
needs to be processed with latex/dvips as its pstricks. (but dropping
the date from the readme also works:-)


More information about the latex3-commits mailing list.