From: Jakub Narebski <jnareb@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Matthieu Moy <Matthieu.Moy@imag.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: asciidoc, was Re: Chicken/egg problem building from a 'git clone'
Date: Fri, 6 Mar 2009 14:15:50 +0100 [thread overview]
Message-ID: <200903061415.50746.jnareb@gmail.com> (raw)
In-Reply-To: <43d8ce650903060428h26392348i4e0db5c23ca57da6@mail.gmail.com>
On Fri, 6 March 2009, John Tapsell wrote:
> 2009/3/6 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> On Fri, 6 Mar 2009, John Tapsell wrote:
>>> 2009/3/6 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>>>> On Fri, 6 Mar 2009, Jakub Narebski wrote:
>>>>> However while toolchain needed to produce documentation (asciidoc +
>>>>> xmlto) isn't, I think, something very common, in my opinion autoconf is
>>>>> something that is present on systems containing other build tools
>>>>> required to build git from sources. So 'configure' branch is not, I
>>>>> think, as necessary as 'html' and 'man' branches; additionally 'html'
>>>>> branch (or the repository used to build documentation, or the byproduct
>>>>> of building documentation) is used to generate on-line docs for git.
>>>>
>>>> Plus, keep in mind that autoconf support is only an afterthought in Git;
>>>> Just running "make" is supposed to work. If it does not, patches are
>>>> certainly welcome, I think.
>>>
>>> Well now that you mention it.. :-)
>>>
>>> It doesn't check for the existance of asciidoc, but blindly assumes it
>>> exists. And even if you do have asciidoc, there's a good chance that
>>> you have the wrong version. The INSTALL file says that asciidoc
>>> requires 8.2.7 but most distros (debian, ubuntu. probably other) have
>>> 8.2.6.
Do you mean here Makefile checks, or do you mean ./configure checking
for existing asciidoc toolchain, and for asciidoc version?
>>> If you compile the docs with the wrong asciidoc version, there is no
>>> warning or error at all. It just builds incorrect man pages.
>>
>> Frankly, I was talking about "make". I never needed asciidoc there.
>>
>> Besides, if it is really an itch of yours, maybe you can come up with a
>> patch checking for a correct asciidoc version? Only if asciidoc would be
>> needed at all, of course.
>
> Yep. I've been looking at it for the last half hour, but configure.ac
> syntax defeats me :-D (I figured getting the check into configure.ac
> would be a good first start)
Errr... doesn't configure.ac have checking for asciidoc version? Search
for AC_CHECK_PROGS(ASCIIDOC, [asciidoc]). Perhaps tests should be more
detailed, or something...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-03-06 13:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 4:09 Chicken/egg problem building from a 'git clone' Joi Ellis
2009-02-06 4:32 ` Johannes Schindelin
2009-02-06 4:45 ` Joi Ellis
2009-02-06 5:12 ` Miles Bader
2009-02-06 5:36 ` Junio C Hamano
2009-02-06 5:49 ` Miles Bader
2009-02-06 8:12 ` Junio C Hamano
2009-02-06 9:31 ` Miles Bader
2009-02-06 10:28 ` Junio C Hamano
2009-02-06 10:35 ` Miles Bader
2009-02-06 19:25 ` Jeff King
2009-02-06 22:12 ` Junio C Hamano
2009-03-01 15:56 ` Joi Ellis
2009-03-01 16:34 ` Björn Steinbrink
2009-03-05 9:06 ` Andreas Ericsson
2009-03-05 11:37 ` John Tapsell
2009-03-05 12:06 ` Jeff King
2009-03-05 12:38 ` Matthieu Moy
2009-03-05 12:45 ` Jeff King
2009-03-06 10:39 ` Jakub Narebski
2009-03-06 10:51 ` Matthieu Moy
2009-03-06 11:04 ` Johannes Schindelin
2009-03-06 11:27 ` John Tapsell
2009-03-06 12:02 ` asciidoc, was " Johannes Schindelin
2009-03-06 12:28 ` John Tapsell
2009-03-06 13:15 ` Jakub Narebski [this message]
2009-03-06 13:39 ` John Tapsell
2009-02-06 5:14 ` Björn Steinbrink
2009-02-06 11:34 ` Johannes Schindelin
2009-02-06 4:44 ` Björn Steinbrink
2009-02-06 19:06 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903061415.50746.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).