From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Tapsell Subject: Re: asciidoc, was Re: Chicken/egg problem building from a 'git clone' Date: Fri, 6 Mar 2009 12:28:08 +0000 Message-ID: <43d8ce650903060428h26392348i4e0db5c23ca57da6@mail.gmail.com> References: <49AF9601.9060709@op5.se> <43d8ce650903050337n48924fc3l89ef991d578f5849@mail.gmail.com> <20090305120602.GA18717@coredump.intra.peff.net> <20090305124512.GA2723@coredump.intra.peff.net> <43d8ce650903060327l64e76f2al7ec3c2ee76be14eb@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jakub Narebski , Jeff King , Matthieu Moy , Git Mailing List To: Johannes Schindelin X-From: git-owner@vger.kernel.org Fri Mar 06 13:31:10 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LfZCl-0007R1-QH for gcvg-git-2@gmane.org; Fri, 06 Mar 2009 13:31:08 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752404AbZCFM2M convert rfc822-to-quoted-printable (ORCPT ); Fri, 6 Mar 2009 07:28:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750769AbZCFM2M (ORCPT ); Fri, 6 Mar 2009 07:28:12 -0500 Received: from rv-out-0506.google.com ([209.85.198.239]:57031 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751291AbZCFM2L convert rfc822-to-8bit (ORCPT ); Fri, 6 Mar 2009 07:28:11 -0500 Received: by rv-out-0506.google.com with SMTP id g37so478598rvb.1 for ; Fri, 06 Mar 2009 04:28:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=b3oyEyF4tIK8b3NN+93z1UhZHgZY6kPKtqQd5IJRSrA=; b=ooiuI1da5rFby7SX7raQjlwoG7nQKZwMOTw+WUzU8QHGTfoQOFbOTzx/Q6XsFt8hJ6 akMDceAlSyI1SKjWZlVdpek87wHXK+CqGmekLm5RF/wH76jo4SjsmR/Q96YCfzhsShK5 LWsCCBEipDkiAUVKhQTc+2RsAt9KuBkCrkA0E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QB88xxHjsFhHl3DEackRfcp6PuFMnBW8omrVLDekMcWGz+j6Jt3TFfGfJNFMr1vTtB HfSIbXSGP0aa7sJXdrdTHwh1K9jTP4Nl+AHqSps6i4aUVwrxxpCrG7vVlBvEJl3T6swh uuK8HM9ItkCmUDfAvuwyeuYsTZbp2Zd8Q+Hhk= Received: by 10.142.231.7 with SMTP id d7mr1074760wfh.285.1236342489161; Fri, 06 Mar 2009 04:28:09 -0800 (PST) In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: 2009/3/6 Johannes Schindelin : > Hi, > > On Fri, 6 Mar 2009, John Tapsell wrote: > >> 2009/3/6 Johannes Schindelin : >> >> > On Fri, 6 Mar 2009, Jakub Narebski wrote: >> > >> >> Jeff King 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= =2E Can you >> >> >>> give an example? >> >> >> >> >> >> man pages and html docs are commited, but in a separate branch= =2E IOW, >> >> >> Junio abuses Git as a distribution mechanism, but keeps it tot= ally >> >> >> 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 si= milar 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 autoc= onf is >> >> something that is present on systems containing other build tools >> >> required to build git from sources. =C2=A0So 'configure' branch i= s not, I >> >> think, as necessary as 'html' and 'man' branches; additionally 'h= tml' >> >> branch (or the repository used to build documentation, or the byp= roduct >> >> of building documentation) is used to generate on-line docs for g= it. >> > >> > Plus, keep in mind that autoconf support is only an afterthought i= n Git; >> > Just running "make" is supposed to work. =C2=A0If it does not, pat= ches 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. =C2=A0And even if you do have asciidoc, there's a good chanc= e that >> you have the wrong version. =C2=A0 The INSTALL file says that asciid= oc >> requires 8.2.7 but most distros (debian, ubuntu. =C2=A0probably othe= r) have >> 8.2.6. >> If you compile the docs with the wrong asciidoc version, there is no >> warning or error at all. =C2=A0It just builds incorrect man pages. > > Frankly, I was talking about "make". =C2=A0I never needed asciidoc th= ere. > > Besides, if it is really an itch of yours, maybe you can come up with= a > patch checking for a correct asciidoc version? =C2=A0Only 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)