unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Is the autogen directory still needed?
Date: Sat, 26 Oct 2013 15:12:45 -0400	[thread overview]
Message-ID: <drr4b7rglu.fsf@fencepost.gnu.org> (raw)


We added the autogen/ directory ~ 2.5 years ago, when we stopped keeping
configure (at top-level) in the repository. I run a daily cron job that
keeps autogen/configure etc updated.

This requires no effort, but I think it has become pointless, basically
just making noise commits.

The main motivations for adding it, as I see it, were:

1) The developers on MS Windows needed to see any updates for
src/config.h (new defines etc) that might need to be copied to
nt/config.nt, and did not want to want have to run autoconf themselves.

2) People who wanted to build Emacs from bzr on POSIX platforms but were
for some reason unable to install (sufficiently recent) autoconf/automake.


Point 1) no longer applies. Bzr Emacs on MS Windows now requires
autotools, and nt/config.nt is no longer being updated.

Point 2) has never been very convincing IMO. It is very easy to install
autotools. The autogen/copy_autogen alternative is not 100% reliable.

The MS-DOS port is not a relevant factor AFAICS, because no-one builds
it from bzr, and when building from release tarfiles there's no need to
run autotools. If necessary, I could keep just autogen/config.in and
whatever MS-DOS needs (not configure).


I'd keep the part of the cron job that updates loaddefs files (which
does not happen nearly so often), and stop doing the autotools part.

Any opinions?



             reply	other threads:[~2013-10-26 19:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26 19:12 Glenn Morris [this message]
2013-10-26 19:17 ` Is the autogen directory still needed? Paul Eggert
2013-10-26 19:59 ` Eli Zaretskii
2013-10-27  2:08   ` Glenn Morris
2013-10-27  2:11     ` Glenn Morris
2013-10-27  3:54     ` Eli Zaretskii
2013-10-28 21:26       ` Glenn Morris
2013-10-29  3:41         ` Eli Zaretskii
2013-10-29 13:44           ` Stefan Monnier
2013-11-05  8:00             ` Glenn Morris
2013-11-05  8:06               ` Glenn Morris
2013-11-05 16:12               ` Eli Zaretskii
2013-11-20 13:53               ` Xue Fuqiao
2013-10-27  2:57 ` Bruce Korb

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=drr4b7rglu.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@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.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).