On Sun, Apr 03, 2016 at 08:05:17PM +0300, Alex Kost wrote: > Mathieu Lirzin (2016-04-03 19:18 +0300) wrote: > > > * pre-inst-env.in: Move to ... > > * build-aux/pre-inst-env.in: ... here. > > * test-env.in: Move to ... > > * build-aux/test-env.in: ... here. > > * configure.ac (AC_CONFIG_FILES): Adapt to this. > > --- > > build-aux/pre-inst-env.in | 71 +++++++++++++++++++++++++ > > build-aux/test-env.in | 131 > > ++++++++++++++++++++++++++++++++++++++++++++++ > > configure.ac | 5 +- > > pre-inst-env.in | 71 ------------------------- > > test-env.in | 131 > > ---------------------------------------------- > > 5 files changed, 205 insertions(+), 204 deletions(-) > > create mode 100644 build-aux/pre-inst-env.in > > create mode 100644 build-aux/test-env.in > > delete mode 100644 pre-inst-env.in > > delete mode 100644 test-env.in > > Hm, this is a radical change :-) I'm afraid moving "pre-inst-env" may > break workflow of many people. Anyway, if this change will be done, > "guix.texi" should also be adjusted as "pre-inst-env" is mentioned in > the manual multiple times.
I'm not very familiar with autotools, but wouldn't it still be possible to put the generated 'pre-inst-env' in the top-level, even though 'pre-inst-env.in' has moved?
