From: Maxime Devos <maximedevos@telenet.be>
To: Zhu Zihao <all_but_last@163.com>
Cc: guix-devel@gnu.org
Subject: Re: Autotools-generated 'configure' & 'Makefile.in' considered binaries?
Date: Thu, 31 Mar 2022 13:19:17 +0200 [thread overview]
Message-ID: <02f2d0e278a376901aacfa6704cdb42ffdd9891a.camel@telenet.be> (raw)
In-Reply-To: <86tubead8i.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Zhu Zihao schreef op wo 30-03-2022 om 22:31 [+0800]:
> For software developer, they prefer to bundle a generated configure
> script because it will be a bootstrap problem sometimes.
Sometimes that's convenient for upstream, but how is this relevant to
downstream (Guix)? Downstream does not have to follow upstream on all
matters, and for the early packages where there would be bootstrap
problems (GCC, binutils, glibc ...), an exception could be made.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-31 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 12:04 Autotools-generated 'configure' & 'Makefile.in' considered binaries? Maxime Devos
2022-03-30 14:31 ` Zhu Zihao
2022-03-31 11:17 ` Maxime Devos
2022-03-31 11:19 ` Maxime Devos [this message]
2022-03-31 11:22 ` Maxime Devos
2022-03-31 11:27 ` Maxime Devos
2022-03-30 18:55 ` Liliana Marie Prikler
2022-03-30 19:24 ` Maxime Devos
2022-03-31 4:22 ` Liliana Marie Prikler
2022-03-31 11:10 ` Maxime Devos
2022-03-31 18:24 ` Liliana Marie Prikler
2022-03-31 18:31 ` Maxime Devos
2022-03-31 20:11 ` Liliana Marie Prikler
2022-04-01 8:58 ` Ludovic Courtès
2022-04-01 10:03 ` Maxime Devos
2022-04-05 12:06 ` Ludovic Courtès
2022-04-06 16:35 ` Maxim Cournoyer
2022-04-10 20:25 ` Ludovic Courtès
2022-05-02 10:55 ` zimoun
2022-04-01 9:12 ` Jonathan McHugh
-- strict thread matches above, loose matches on Subject: below --
2022-06-29 19:01 Maxime Devos
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=02f2d0e278a376901aacfa6704cdb42ffdd9891a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=all_but_last@163.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).