From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [RFC] Dog food, anyone?
Date: Sat, 28 Apr 2018 12:56:04 +0200
Message-ID: <87604bsipn.fsf@nicolasgoaziou.fr>
References: <87efntod73.fsf@nicolasgoaziou.fr> <87y3h9pmng.fsf@bzg.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]:44467)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fCNWa-0001yr-RV
	for emacs-orgmode@gnu.org; Sat, 28 Apr 2018 06:56:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fCNWa-0003R5-1s
	for emacs-orgmode@gnu.org; Sat, 28 Apr 2018 06:56:16 -0400
In-Reply-To: <87y3h9pmng.fsf@bzg.fr> (Bastien's message of "Fri, 27 Apr 2018
	01:34:43 +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: Bastien <bzg@gnu.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>

Hello,

Bastien <bzg@gnu.org> writes:

> it would be nice to make the switch to org-manual.org for Org 9.2,
> and to delete org.texi entirely from the master branch.

We already switched to "org-manual.org" in the sense that current
"org.texi" is generated from "org-manual.org".

> I guess we need to add some Makefile rules so that "make pdf" first
> exports .org => .texi then exports .texi to .pdf... is that so?

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.

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

Regards,

-- 
Nicolas Goaziou