From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag / cygport not pulling lzip
Date: Sat, 09 Jan 2021 20:08:49 +0100 [thread overview]
Message-ID: <87ft3a7wse.fsf@Rainer.invalid> (raw)
In-Reply-To: <87a6tj9wst.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 08 Jan 2021 18:13:22 +0100")
Achim Gratz writes:
> Since it promises to enable it's use, yes. I wouldn't mind to add a
> dependency to tar also.
Since lzip is not a very large package and tar just released a new
version… should I add the dependency or should I keep things as they
are?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
next prev parent reply other threads:[~2021-01-09 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 7:38 Marco Atzeri
2021-01-08 13:23 ` ASSI
2021-01-08 13:58 ` Marco Atzeri
2021-01-08 14:21 ` Jon Turney
2021-01-08 16:52 ` Brian Inglis
2021-01-08 17:13 ` Achim Gratz
2021-01-08 18:09 ` Brian Inglis
2021-01-08 19:11 ` Achim Gratz
2021-01-11 22:05 ` Brian Inglis
2021-01-12 16:28 ` Brian Inglis
2021-01-12 19:46 ` ASSI
2021-01-09 19:08 ` Achim Gratz [this message]
2022-08-14 19:07 Hannes Mueller
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=87ft3a7wse.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).