From: Zhu Zihao <all_but_last@163.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel@gnu.org
Subject: Re: Autotools-generated 'configure' & 'Makefile.in' considered binaries?
Date: Wed, 30 Mar 2022 22:31:29 +0800 [thread overview]
Message-ID: <86tubead8i.fsf@163.com> (raw)
In-Reply-To: <9c2ca57d59672fc4f9ebc0230b08d8953030a456.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
We can make GNU build system tries autoreconf or autogen.sh first if we
encounter some build issues. But I don't think it's a good idea to
remove configure script in the snippet of origin. Because you can't
track all files that generated by Autotools. It is also burden for
packager to pick the build-time dependencies like libtool,
autoconf-archive, gnulib etc. if we force all autotools baseed packages
use autoreconf
For software developer, they prefer to bundle a generated configure
script because it will be a bootstrap problem sometimes.
A simple examples,the m4 macro GUILE_PKG defined in guile.m4 helps
autotools to check guile installation. If there's no generated configure
script. Software user should have guile.m4 to generate configure script.
A macro that detects guile installation requires a guile installation to
work. Catch 22 :)
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-03-31 5:45 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 [this message]
2022-03-31 11:17 ` Maxime Devos
2022-03-31 11:19 ` Maxime Devos
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=86tubead8i.fsf@163.com \
--to=all_but_last@163.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).