From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Kei Kebreau <kei@openmailbox.org>, 27898@debbugs.gnu.org
Subject: [bug#27898] [PATCH 2/2] gnu: Put autoconf-related phases immediately after the 'unpack phase.
Date: Wed, 2 Aug 2017 15:45:15 -0400 [thread overview]
Message-ID: <20170802194515.GC13105@jasmine.lan> (raw)
In-Reply-To: <87k22lwys2.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Wed, Aug 02, 2017 at 09:33:01PM +0200, Marius Bakke wrote:
> Kei Kebreau <kei@openmailbox.org> writes:
[... move autoconf phases ...]
> Phew! This too will cause a lot of rebuilds, but I guess we could put it
> on 'staging'. It would have to be committed just before starting it to
> reduce the amount of merge conflicts.
Agreed
> That said, I'm not sure how necessary this change is, but I don't have a
> strong argument against it. Other opinions welcome!
I guess there is a correct ordering and an incorrect ordering, depending
on whether or not these phases should happen before or after the shebang
patching phases. Does it work if it happens before the shebangs are
patched?
> Maybe we could add an '#:autoreconf?' parameter to gnu-build-system,
> which runs `autoreconf -vif` in a phase and automatically pulls in
> automake and autoconf (and probably also libtool). Thoughts?
Interesting!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-02 19:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 7:18 [bug#27898] Clean-up of package phases Kei Kebreau
2017-08-01 7:21 ` [bug#27898] [PATCH 1/2] gnu: Use 'modify-phases' syntax Kei Kebreau
2017-08-01 7:21 ` [bug#27898] [PATCH 2/2] gnu: Put autoconf-related phases immediately after the 'unpack phase Kei Kebreau
2017-08-02 19:33 ` Marius Bakke
2017-08-02 19:45 ` Leo Famulari [this message]
2017-08-02 20:31 ` Kei Kebreau
2017-08-02 22:44 ` Leo Famulari
2017-08-27 10:48 ` Marius Bakke
2017-08-02 19:12 ` [bug#27898] [PATCH 1/2] gnu: Use 'modify-phases' syntax Marius Bakke
2017-08-02 19:41 ` Leo Famulari
2017-08-02 20:08 ` Marius Bakke
2017-08-02 20:38 ` Kei Kebreau
2017-08-02 22:46 ` Leo Famulari
2017-08-02 22:54 ` Marius Bakke
2017-08-02 23:06 ` Marius Bakke
2017-08-27 10:44 ` Marius Bakke
2017-08-28 18:06 ` Kei Kebreau
2017-08-28 20:49 ` Marius Bakke
2017-08-28 23:00 ` Kei Kebreau
2017-08-31 12:59 ` Kei Kebreau
2017-08-31 16:59 ` Marius Bakke
2017-09-01 8:17 ` Ludovic Courtès
2017-09-04 4:13 ` Kei Kebreau
2017-09-04 20:37 ` Marius Bakke
2017-10-18 23:29 ` bug#27898: Clean-up of package phases Ricardo Wurmus
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=20170802194515.GC13105@jasmine.lan \
--to=leo@famulari.name \
--cc=27898@debbugs.gnu.org \
--cc=kei@openmailbox.org \
--cc=mbakke@fastmail.com \
/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/guix.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.