From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: autoconf
Date: Wed, 1 Dec 2021 23:08:44 -0700 [thread overview]
Message-ID: <2262e475-e281-bfc9-b00c-c471b8ad58cb@SystematicSw.ab.ca> (raw)
In-Reply-To: <87mtlk6qvq.fsf@Rainer.invalid>
On 2021-12-01 12:56, Achim Gratz wrote:
> Marco Atzeri via Cygwin-apps writes:
>> anyone working or planning to take over the Autoconf ?
> I haven't, but looking at the packages I picked up maybe I should.
>> The 2.71 version seems becoming popular in some package source code.
> How likely is it that they actually rely on that version already?
Somewhat likely for some GNU packages and gnulib macros that specify
version prereqs: AC_PREREQ is used in 80 packages I have sources for.
After that version released in January, I've only had to patch one
package so far, which specified it in August, and they later reduced it
after discussion with distro package maintainers:
$ grep 'AC_PREREQ(\[2\.[0-9]\+\])' */*.patch
bison/bison-3.7.90-revert-autoconf-upgrade.patch:-AC_PREREQ([2.71])
bison/bison-3.7.90-revert-autoconf-upgrade.patch:+AC_PREREQ([2.68])
wget2/configure-ac.upstream.patch:-AC_PREREQ([2.67])
wget2/configure-ac.upstream.patch:+AC_PREREQ([2.69])
Xcurses/x11-aclocal-m4-libtoolize.patch:+[AC_PREREQ([2.62])dnl We use
AC_PATH_PROGS_FEATURE_CHECK
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-12-02 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 20:29 autoconf Marco Atzeri
2021-12-01 19:56 ` autoconf Achim Gratz
2021-12-02 6:08 ` Brian Inglis [this message]
2021-12-02 7:23 ` autoconf ASSI
2021-12-02 9:21 ` autoconf Corinna Vinschen
2021-12-02 10:15 ` autoconf Jan Nijtmans
2021-12-02 10:40 ` autoconf Corinna Vinschen
2021-12-02 10:45 ` autoconf Jan Nijtmans
2021-12-02 13:18 ` autoconf ASSI
2021-12-02 13:32 ` autoconf Corinna Vinschen
2021-12-02 16:36 ` autoconf Ken Brown
2021-12-02 13:19 ` autoconf Ken Brown
2021-12-02 18:18 ` autoconf Achim Gratz
2021-12-02 19:41 ` autoconf Achim Gratz
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=2262e475-e281-bfc9-b00c-c471b8ad58cb@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.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.
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).