On 13/11/10 21:04, Arnaud Quette wrote:
2010/11/13 Sebastian Pipping
On 11/13/10 00:40, Arnaud Quette wrote:
>
> 2010/11/12 Stuart Rackham wrote:
>
>
> On 12/11/10 10:45, Arnaud Quette wrote:
>
> (...)
> just a question, because NUT' configure script is
checking this:
> a2x version is still 8.6.1 while asciidoc is already 8.6.3.
> do you plan to also bump a2x version?
>
>
> Thanks for spotting that Arnaud, I've updated it in the trunk.
>
>
> welcome ;-)
>
> you may want to automate this and manage it at a central location, to
> avoid missing it during release.
> you already have it btw in your configure.ac
<http://configure.ac> <http://configure.ac> (even
> more outdated), you just need to:
> - create {asciidoc,a2x}.py.in <http://py.in> <http://py.in>
> - reference these in configure.ac->AC_OUTPUT
> - patch these file with
> VERSION = @PACKAGE_VERSION@
>
> I can provide a patch if needed.
That would make develeopment of the Python code rather difficult.
not sure what you mean here.
if you think about syntax highlighting, then most (if not all) modern
editors handle this.
An alternative could be creating a file "version.py" and import that
from the main code.
well, it simplifies the code somehow, but not the distribution, since
you have to ship, and be able to find your version.py
to answer to Stuart, the .in files are simply the .py counter part,
renamed and replacing the version data.
ie, a2x.py.in <http://a2x.py.in> is simply a copy of a2x.py with VERSION
= @PACKAGE_VERSION@
that being said, creating an asciidoc-version.py, then distributed in
the sysconfig directory might best apply here.
@Stuart: up to you...
The current situation is not ideal, the version numbers are in 4 files:
asciidoc.py, a2x.py, common.aap and configure.ac.
There is a precedence of sorts in that the Makefile patches asciidoc.py and
a2x.py with the system CONF_DIR (see the fixconfpath target in Makefile.in), the
nice thing about this is that it doesn't involve extra files, but this is an
install-time function not a build-time function (which is why it's performed by
make and not by AAP).
The build gets done by AAP so my feeling is that AAP should patch the various
files from the master values in common.aap, there is already a vers target in
main.aap (currently all it does is print the version number and release date but
it could be made to do a version number update).
Cheers, Stuart
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
--
You received this message because you are subscribed to the Google
Groups "asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
