unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Using Org as the source format to generate org.texi
Date: Tue, 13 Mar 2018 16:47:03 +0000	[thread overview]
Message-ID: <873713dit4.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvwoyg5ff1.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 13 Mar 2018 08:29:10 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Oh dear. I was hoping not to side-track the issue.
>> Yes, it's a hypothetical Emacs where org is hosted in ELPA not in
>> emacs.git, but still distributed with the Emacs tar ball. And the
>> question is, what if packages other than org used org-mode for their
>> manuals.
>
> Actually, as long as these other manuals are in ELPA packages which have
> `org` in their "Package-Requires:", I think it'd still be fine.
> So it's probably not something that we need to worry about.

Yeah, agreed that would be a solution. Given the time scales, we could
also look at adding another heading to ELPA packages, which would,
effectively, specify a build time dependency.

The key point here, is that this is far from a show stopper; there are
clear solutions, and we have lots of time to think about them.

Phil



  reply	other threads:[~2018-03-13 16:47 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 18:04 Using Org as the source format to generate org.texi Bastien
2018-03-06 20:20 ` Stefan Monnier
2018-03-06 20:24   ` Kaushal Modi
2018-03-06 21:54   ` Achim Gratz
2018-03-07  0:22   ` Bastien
2018-03-07 17:43     ` Eli Zaretskii
2018-03-07 17:52       ` Kaushal Modi
2018-03-08 10:04         ` Bastien Guerry
2018-03-08  7:28       ` Michael Albinus
2018-03-08 10:06         ` Bastien Guerry
2018-03-08 10:13       ` Bastien Guerry
2018-03-07 17:39   ` Glenn Morris
2018-03-07 22:57   ` Richard Stallman
2018-03-09 11:30     ` Bastien
2018-03-10 21:26     ` Nicolas Goaziou
2018-03-11  3:40       ` Eli Zaretskii
2018-03-11 14:59       ` Michael Albinus
2018-03-11 18:13         ` Nicolas Goaziou
2018-03-11 23:26       ` Richard Stallman
2018-03-12 14:07         ` Nicolas Goaziou
2018-03-12 15:51           ` Eli Zaretskii
2018-03-12 16:42             ` Nicolas Goaziou
2018-03-12 17:32               ` Eli Zaretskii
2018-03-12 17:57                 ` Nicolas Goaziou
2018-03-12 20:16                   ` Eli Zaretskii
2018-03-12 21:37                     ` Nicolas Goaziou
2018-03-13 15:55                       ` Eli Zaretskii
2018-03-13 17:24                         ` Nicolas Goaziou
2018-03-13 17:43                           ` Eli Zaretskii
2018-03-13 21:37                             ` Nicolas Goaziou
2018-04-14 17:10                         ` @key{...} mis-use (was: Using Org as the source format to generate org.texi) Nicolas Goaziou
2018-04-19  9:22                           ` Eli Zaretskii
2018-03-06 21:30 ` Using Org as the source format to generate org.texi Paul Eggert
2018-03-07  0:19   ` Bastien
2018-03-07  1:08     ` Paul Eggert
2018-03-07  7:33       ` Achim Gratz
2018-03-09 17:52         ` Achim Gratz
2018-03-09 18:02           ` Paul Eggert
2018-03-09 18:23             ` Achim Gratz
2018-03-07 17:41       ` Glenn Morris
2018-03-09 11:19         ` Phillip Lord
2018-03-12 17:12           ` Glenn Morris
2018-03-09 17:39         ` Achim Gratz
2018-03-10 20:07           ` Phillip Lord
2018-03-11  3:00             ` Paul Eggert
2018-03-11  3:55               ` Stefan Monnier
2018-03-11 21:46                 ` Phillip Lord
2018-03-12 21:04             ` Radon Rosborough
2018-03-13  9:10               ` Phillip Lord
2018-03-13 12:29                 ` Stefan Monnier
2018-03-13 16:47                   ` Phillip Lord [this message]
2018-04-14 19:15 ` Joshua Branson

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873713dit4.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).