mirror of
git://git.sv.gnu.org/autoconf
synced 2025-01-18 10:45:15 +08:00
TODO: less pressure on 2.50.
This commit is contained in:
parent
0d2a305062
commit
d293db9198
26
TODO
26
TODO
@ -9,10 +9,6 @@ these suggestions... their presence here doesn't imply my endorsement.
|
||||
|
||||
* Autoconf 2.50
|
||||
|
||||
** AC_SYS_INTERPRETER
|
||||
Defines $interpval. This is not a standard name. Do we want to keep
|
||||
this? Clarify our policy on those names.
|
||||
|
||||
** AC_INIT(PACKAGE)
|
||||
Decide with the team whether they prefer that AC_PACKAGE_NAME etc. be
|
||||
a macro, or a shell variable ac_package_name. Had we used AC_PACKAGE
|
||||
@ -21,15 +17,6 @@ think of the capitalization! For instance this package is named
|
||||
`Autoconf', but the tarball is `autoconf-'. What of the space?
|
||||
Do we need another user input for the name of the tarball?
|
||||
|
||||
** config.status
|
||||
Lars seemed to need to be able to apply both the AC_SUBST and
|
||||
AC_DEFINE transformation on a single file, which implies that we must
|
||||
be able to have `.in' files either in srcdir or in builddir. In fact,
|
||||
have a look at the configuration of Zsh: they patch config.status on
|
||||
the fly to have it look for the files in builddir instead of srcdir!!!
|
||||
There is a real problem, Autoconf must help. BTW, why do they need
|
||||
that?
|
||||
|
||||
** Doc: autoconf
|
||||
Document --install. Should --install `fix' configure.in for the user?
|
||||
|
||||
@ -104,6 +91,10 @@ From: Roland McGrath <roland@gnu.ai.mit.edu>
|
||||
|
||||
* Autoconf 2.51 or so
|
||||
|
||||
** AC_SYS_INTERPRETER
|
||||
Defines $interpval. This is not a standard name. Do we want to keep
|
||||
this? Clarify our policy on those names.
|
||||
|
||||
** AC_PROVIDE
|
||||
I think it is the epilogue that should provide, not the prologue. Not
|
||||
clear: there are risks of circular dependencies :(. In fact the
|
||||
@ -139,6 +130,15 @@ replacement function, it's unreadable.
|
||||
** Allow --recursive to config.status
|
||||
So that --recheck does not pass --no-recursive to configure.
|
||||
|
||||
** config.status
|
||||
Lars seemed to need to be able to apply both the AC_SUBST and
|
||||
AC_DEFINE transformation on a single file, which implies that we must
|
||||
be able to have `.in' files either in srcdir or in builddir. In fact,
|
||||
have a look at the configuration of Zsh: they patch config.status on
|
||||
the fly to have it look for the files in builddir instead of srcdir!!!
|
||||
There is a real problem, Autoconf must help. BTW, why do they need
|
||||
that?
|
||||
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user