From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: [RFC] Dog food, anyone?
Date: Sat, 28 Apr 2018 14:43:38 +0200
Message-ID: <87in8bv6v9.fsf@gnu.org>
References: <87efntod73.fsf@nicolasgoaziou.fr> <87y3h9pmng.fsf@bzg.fr>
	<87604bsipn.fsf@nicolasgoaziou.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59984)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <bzg@gnu.org>)
	id 1fCPCb-0007kB-I9
	for emacs-orgmode@gnu.org; Sat, 28 Apr 2018 08:43:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bzg@gnu.org>) id 1fCPCW-0008Rp-MO
	for emacs-orgmode@gnu.org; Sat, 28 Apr 2018 08:43:45 -0400
In-Reply-To: <87604bsipn.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of
	"Sat, 28 Apr 2018 12:56:04 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, Achim Gratz <Stromeko@stromeko.de>
Cc: Org Mode List <emacs-orgmode@gnu.org>

Hi Nicolas,

I'm cc'ing Achim as I seem to remember he offered to help writing
needed rules for the switch to org-manual.org to be complete.

> I guess we could extend the "info" rule to generate the ".texi" file out
> of "org-manual.org" first. For example, in "doc/Makefile",  we could
> either add a pre-requisite to the following rule:
>
>   info:             org
>
> e.g.,
>
>   info:         org.texi org
>
>   org.texi: org-manual.org
>        $(BATCH) \
>          --eval '(add-to-list '"'"'load-path "../lisp")' \
>          --eval '(load "org-compat.el")' \
> 	 --eval '(load "../mk/org-fixup.el")' \
> 	 --eval '(org-generate-texinfo-manual "$<" "@$")'
>        $(MAKEINFO) --no-split $< -o $@
>
> assuming `org-generate-texinfo-manual' is defined in "org-fixup.el".
>
> However, the above may require to mess with the match-all rule
>
>   .SUFFIXES:	.texi .tex .txt _letter.tex
>   
>   %:		%.texi org-version.inc
>   	$(MAKEINFO) --no-split $< -o $@
>
> In particular, we might drop the "org-version.inc" file. But the build
> system is tricky, I admit I do not understand it totally.

Achim, what do you think?

If we can drop the org-version.inc, that's even better.

> BTW, I wonder why the build system needs to create an "org" file,
> without extension, equivalent to "org.info".

I guess that's a leftover from old times, when the .info extension on
info files was not systematic.

-- 
 Bastien