git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Tapsell <johnflux@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>, Jeff King <peff@peff.net>,
	Matthieu Moy <Matthieu.Moy@imag.fr>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Chicken/egg problem building from a 'git clone'
Date: Fri, 6 Mar 2009 11:27:21 +0000	[thread overview]
Message-ID: <43d8ce650903060327l64e76f2al7ec3c2ee76be14eb@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903061203270.10279@pacific.mpi-cbg.de>

2009/3/6 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> Hi,
>
> On Fri, 6 Mar 2009, Jakub Narebski wrote:
>
>> Jeff King <peff@peff.net> writes:
>> > On Thu, Mar 05, 2009 at 01:38:27PM +0100, Matthieu Moy wrote:
>> >
>> >>>> * we have lots other files in git.git that are autogenerated (the
>> >>>> documentation files, for example)
>> >>>
>> >>> I'm not aware of any auto-generated files that are checked in. Can you
>> >>> give an example?
>> >>
>> >> man pages and html docs are commited, but in a separate branch. IOW,
>> >> Junio abuses Git as a distribution mechanism, but keeps it totally
>> >> separate from the actual sources.
>> >
>> > OK, true; but that is a totally different mechanism, unless the proposal
>> > is to autobuild a "this would be the release tarball" branch similar to
>> > html and man branches.
>>
>> I thnk the proposal was to have 'configure' branch with configure
>> script built, similar to how 'html' and 'man' branches have built
>> documentation in HTML and manpages format.
>>
>> 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.
If you compile the docs with the wrong asciidoc version, there is no
warning or error at all.  It just builds incorrect man pages.

John

  reply	other threads:[~2009-03-06 11:28 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 [this message]
2009-03-06 12:02                                       ` asciidoc, was " Johannes Schindelin
2009-03-06 12:28                                         ` John Tapsell
2009-03-06 13:15                                           ` Jakub Narebski
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=43d8ce650903060327l64e76f2al7ec3c2ee76be14eb@mail.gmail.com \
    --to=johnflux@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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).