From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Date: Sat, 09 Jul 2011 10:38:23 +0200 [thread overview]
Message-ID: <87vcvbn91c.fsf@gnu.org> (raw)
In-Reply-To: <87vcvckm0s.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 09 Jul 2011 08:26:11 +0200")
Hi Achim,
Achim Gratz <Stromeko@nexgo.de> writes:
> A Makefile is not the place to pull stunts, IMHO. Whenever you feel
> that should become necessary, maybe it's time to go autoconf or some
> similar mechanism. I don't think that's the right thing to do for
> org-mode, since it again adds some dependency on other software.
I'm not a big fan of considering autoconf either.
Wild guess:
- 90% of Org users use the Emacs version;
- for those who do not, 90% can live with the current Makefile;
- for the 10% that cannot run the Makefile:
- 50% will just locally add the right load-path and info-path
- 50% will need more install information.
The solution I suggest is to clearly document the few exceptions
(0.5%) for those who need them.
--
Bastien
next prev parent reply other threads:[~2011-07-09 8:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 1:11 patch org-mode Makefile - solve a couple debian build problems and a slackware build problem Jude DaShiell
2011-07-07 14:42 ` Bastien
2011-07-08 7:33 ` Jude DaShiell
2011-07-08 8:21 ` Bastien
2011-07-08 9:10 ` Nick Dokos
2011-07-08 9:29 ` Bastien
2011-07-08 10:08 ` Andrea Crotti
2011-07-08 22:07 ` Achim Gratz
2011-07-08 22:50 ` Nick Dokos
2011-07-09 6:26 ` Achim Gratz
2011-07-09 8:38 ` Bastien [this message]
2011-07-09 16:00 ` Nick Dokos
2011-07-09 16:40 ` Achim Gratz
2011-07-09 20:45 ` Jude DaShiell
2011-07-10 1:40 ` Nick Dokos
2011-07-10 1:44 ` Nick Dokos
2011-07-10 8:16 ` Jude DaShiell
2011-07-10 7:24 ` Achim Gratz
2011-07-10 8:13 ` Jude DaShiell
2011-07-10 8:40 ` Achim Gratz
2011-07-08 10:34 ` Jambunathan K
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcvbn91c.fsf@gnu.org \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).