all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r109306: Use an include file	in configure.ac's AH_BOTTOM
Date: Tue, 31 Jul 2012 22:17:53 +0300	[thread overview]
Message-ID: <83obmveo4e.fsf@gnu.org> (raw)
In-Reply-To: <nzobmvizdl.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: lekktu@gmail.com,  emacs-devel@gnu.org
> Date: Tue, 31 Jul 2012 14:01:10 -0400
> 
> Eli Zaretskii wrote:
> 
> > Btw, if the idea of conf_post.h is to be the only place of
> > system-dependent configury that isn't autoconfiscated
> 
> That wasn't particularly the intention, it was just necessary to work
> around an autoconf issue;
> http://lists.gnu.org/archive/html/autoconf/2006-10/msg00020.html

OK, but then what's The Plan wrt this stuff?  Are we waiting for
Autoconf to be fixed?  Is this stuff going to be left in a separate
header for the observable future?  Something else?

I mean, it's hard to follow suit on non-Posix platforms, when the
maintainer's intent on Posix was not revealed (apologies if it was and
I missed that).

> > , and if we want to remove src/s/ altogether, would it be okay to move
> > stuff from msdos.h and ms-w32.h into conf_post.h?
> 
> I'm obviously hoping Someone (TM) will remove s/msdos.h and s/ms-w32.h,
> either by moving them to the nt/ or msdos/ directory (or if all else
> fails, to src/), or by folding them in to config.nt or some other
> place...

There's any number of possible ways to do this.  Which one is the
best, I cannot decide without knowing your goal with this stuff, which
is clearly platform-dependent.  The removal of things from src/s/*.h
is going on for some time, but the last thing I expected to see at its
end is a bunch platform-specific macros on a platform-independent
header.  It's confusing.

> AMPERSAND_FULL_NAME and subprocesses obviously belong in configure.ac; I
> moved them.

What about SYSTEM_PURESIZE_EXTRA?  conf_post.h defines that for NS and
Darwin; should I move the msdos.h definitions there as well?  If not,
why not?

Or what about NULL_DEVICE or SEPCHAR? should they be autoconfiscated
(in which case they can be removed from s/msdos.h)?

There are more questions like this, and they get in the way of making
the decision what to do with src/s/ms*.h.

TIA



  reply	other threads:[~2012-07-31 19:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1SvyHP-00051u-7i@vcs.savannah.gnu.org>
2012-07-31 12:10 ` [Emacs-diffs] /srv/bzr/emacs/trunk r109306: Use an include file in configure.ac's AH_BOTTOM Juanma Barranquero
2012-07-31 12:23   ` Juanma Barranquero
2012-07-31 17:09   ` Eli Zaretskii
2012-07-31 17:15     ` Juanma Barranquero
2012-07-31 17:31       ` Eli Zaretskii
2012-07-31 17:45         ` Eli Zaretskii
2012-07-31 18:01           ` Glenn Morris
2012-07-31 19:17             ` Eli Zaretskii [this message]
2012-07-31 19:28               ` Glenn Morris
2012-07-31 19:35                 ` Glenn Morris
2012-07-31 19:40                   ` Juanma Barranquero
2012-07-31 20:04                   ` Eli Zaretskii
2012-07-31 20:22                     ` Glenn Morris
2012-07-31 20:33                   ` Paul Eggert
2012-07-31 20:03                 ` Eli Zaretskii
2012-07-31 19:37         ` Juanma Barranquero
2012-07-31 19:58         ` Juanma Barranquero
2012-07-31 20:06           ` Eli Zaretskii
2012-07-31 20:18             ` Juanma Barranquero
2012-07-31 20:27   ` Glenn Morris
2012-07-31 20:36     ` Glenn Morris
2012-07-31 20:43       ` Paul Eggert
2012-07-31 21:37       ` Juanma Barranquero
2012-07-31 22:50         ` Glenn Morris
2012-07-31 22:57           ` Juanma Barranquero
2012-07-31 23:04             ` Glenn Morris
2012-07-31 23:04           ` Juanma Barranquero

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

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

  git send-email \
    --in-reply-to=83obmveo4e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=rgm@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.