From: Leo Famulari <leo@famulari.name>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] build: Move environment scripts to 'build-aux' directory.
Date: Sun, 3 Apr 2016 14:19:19 -0400 [thread overview]
Message-ID: <20160403181919.GB9334@jasmine> (raw)
In-Reply-To: <871t6m39o2.fsf@gmail.com>
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?
next prev parent reply other threads:[~2016-04-03 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 16:18 [PATCH 0/2] Clean repository top-level directory Mathieu Lirzin
2016-04-03 16:18 ` [PATCH 1/2] build: Move included files to subdirectories Mathieu Lirzin
2016-04-04 2:36 ` Eric Bavier
2016-04-14 17:46 ` Ludovic Courtès
2016-04-14 22:55 ` Mathieu Lirzin
2016-04-16 22:54 ` Ludovic Courtès
2016-05-21 21:41 ` Mathieu Lirzin
2016-05-22 20:33 ` Ludovic Courtès
2016-04-03 16:18 ` [PATCH 2/2] build: Move environment scripts to 'build-aux' directory Mathieu Lirzin
2016-04-03 17:05 ` Alex Kost
2016-04-03 17:18 ` Mathieu Lirzin
2016-04-03 21:56 ` Alex Kost
2016-04-03 18:19 ` Leo Famulari [this message]
2016-04-03 19:19 ` Mathieu Lirzin
2016-04-14 17:48 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160403181919.GB9334@jasmine \
--to=leo@famulari.name \
--cc=alezost@gmail.com \
--cc=guix-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/guix.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).