From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: CI scallywag setup/cygport/autoconf missing autoconf-archive pkg
Date: Sat, 02 Oct 2021 06:15:10 +0200 [thread overview]
Message-ID: <87tui0jc4x.fsf@Rainer.invalid> (raw)
In-Reply-To: <9b1ea563-f5c0-04f2-d117-6f792b6cdb94@SystematicSw.ab.ca> (Brian Inglis's message of "Wed, 29 Sep 2021 22:15:53 -0600")
Brian Inglis writes:
> As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
> would be the more appropriate place for an autoconf-archive
> requirement, otherwise cygport would have to require it, which is not
> so obvious.
No. If a build needs autoconf-archive then require it there. The whole
point of having things in separate packages is that you do not have to
install things you don't need. Neither autottols nor cygport require
this package in any way.
Off-tangent: cygport has entirely too many dependencies already which we
can't help with our current package system. I'd love to have a way for
these dependencies not to creep into each build.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2021-10-02 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 4:15 Brian Inglis
2021-10-01 21:37 ` Yaakov Selkowitz
2021-10-02 0:06 ` Brian Inglis
2021-10-02 4:15 ` Achim Gratz [this message]
2021-10-02 5:48 ` Brian Inglis
2021-10-02 14:13 ` Ken Brown
2021-10-02 16:35 ` Brian Inglis
2021-10-03 19:14 ` Brian Inglis
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=87tui0jc4x.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).