From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: Autotools-generated 'configure' & 'Makefile.in' considered binaries?
Date: Thu, 31 Mar 2022 06:22:04 +0200 [thread overview]
Message-ID: <b95621ad7b434b7c2f26b2bd66f45851a48d8030.camel@gmail.com> (raw)
In-Reply-To: <0bf2fc29d29871346f726b721bc2ac934a7891ab.camel@telenet.be>
Am Mittwoch, dem 30.03.2022 um 21:24 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op wo 30-03-2022 om 20:55 [+0200]:
> > Note that many autotools-based packages already require the
> > addition of autoconf and friends due to being pulled from git.
> > That being said, it's somewhat hard to argue for completely
> > dropping them, because
> > a. simply matching files via ".in" suffix would be error-prone
> > b. autoreconf should regenerate these files regardless
> > Therefore, my counter-proposal would be to just simply always run
> > the bootstrap script or autoreconf, even if the respective files
> > are tarballed, as well as adding autoconf and automake to the
> > implicit native inputs of gnu build system.
>
> It should be possible to look for ‘# Generated by GNU Autoconf’ and
> ‘# Makefile.in generated by automake’ lines in some 'find-generated-
> autotools-fies’or something.
I don't think that will work correctly. Case in point: pre-inst-env in
the Guix source tree.
> Adding autoconf & automake seems a bit much to me (gnu-build-system
> is not necessarily autotools-build-system, the exact required version
> of autoconf & automake can vary), but otherwise your proposal seems
> good to me.
We could drop both from the deriving system or simply define a constant
%implicit-gnu-inputs-no-autotools (name subject to bikeshedding).
next prev parent reply other threads:[~2022-03-31 4:22 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
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 [this message]
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=b95621ad7b434b7c2f26b2bd66f45851a48d8030.camel@gmail.com \
--to=liliana.prikler@gmail.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).