emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: makefile regression
Date: Thu, 24 May 2012 08:12:14 -0400	[thread overview]
Message-ID: <rmik401dbhd.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87aa0yi0er.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 24 May 2012 08:00:12 +0200")

[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]


I don't really object to using GNU make; enough things require it
(probably emacs does too) that it's already installed.  It's more that
"anyone using a makefile will use gnu make" isn't a valid assumption,
especially when the documentation says "type make".

  At the very start of my Makefile branch I stated that I will use GNU
  make since the old make file already used some GNU make features.  This
  will be documented when it gets released.  Using GNU make features
  helped to keep things a bit more maintenance friendly, but before other
  things, I have a reliable documentation of what it is supposed to do and
  can be reasonably sure that it actually does that across a range of
  platforms.

It seems easy enough to document the requirement in README in the
sources, where programs traditonally list their prerequisites; I looked
there and in the usual other files and found no such requirement
explained.  I don't understand why it makes sense to defer adjusting the
source to explain what's needed until its tagged, but maybe you don't
mean that.

Separately, that would be a good place to explain what version of emacs
are supported.  I am running 24 and thus not running into too new/old,
but I now realize that's an obvious question the answer to which my
attempt to find out if the requirement to use GNU Make was documented
should have led me across.

  > This seems unfortunate; I don't understand why building org has to be so
  > complicated.  If it is complicated, it seems best to use
  > autoconf/automake, which already have worked out most of the portability
  > issues.

  Please, let's not go there.  I will implement a facility to build an
  in-place orgmode without any support from make at all.  It appears that
  this would be enough for your use-case, but I'd still still suggest to
  use GNU make.

I did use GNU make.   My reaction was not to GNU make, but that it
wasn't obvious in a minute or two what all the makefile complexity was
for.

  > (I haven't seen any discussion, but I confess to not quite keeping up
  > with with emacs-orgmode traffic.)

  It seems a better idea to stay on maint rather than on master then.

By not quite keeping up I mean that I scan all the subject lines and
read some things.  Almost all if not all of my problems on master over
the last few years have been running into real bugs.


Thanks,
Greg

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2012-05-24 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 14:43 makefile regression Greg Troxel
2012-05-22 16:20 ` Bastien
2012-05-24  6:00 ` Achim Gratz
2012-05-24  9:05   ` Bastien
2012-05-24 12:12   ` Greg Troxel [this message]
2012-05-24 17:15     ` Achim Gratz
2012-05-25  0:08       ` [PATCH] Add section describing prerequisites Greg Troxel
2012-05-25 22:33         ` Bastien
2012-05-25 23:52           ` Greg Troxel
2012-05-25  0:12       ` makefile regression Greg Troxel
2012-05-25 18:43         ` Achim Gratz

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=rmik401dbhd.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --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).