public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] lz4 1.7.5-1
Date: Tue, 27 Feb 2018 01:20:00 -0000	[thread overview]
Message-ID: <24d07cdb-7ad9-0ff0-65df-18502f71da72@SystematicSw.ab.ca> (raw)
In-Reply-To: <auto-000003744910@fwd2.webnames.ca>

On 2017-09-03 20:02, Yaakov Selkowitz wrote:
> The following packages have been uploaded to the Cygwin distribution:
> * lz4-1.7.5-1
> * liblz4_1-1.7.5-1
> * liblz4-devel-1.7.5-1
> * mingw64-i686-lz4-1.7.5-1
> * mingw64-x86_64-lz4-1.7.5-1
> LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding. The 
> most important design principle behind LZ4 is simplicity.
> Upstream versioning has changed to a more traditional form in this release.

Is lz4 statically built with and not depend on liblz4_1?

Setup is not upgrading lz4 from 131 - should the solver be picking that up now?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

       reply	other threads:[~2018-02-27  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <auto-000003744910@fwd2.webnames.ca>
2018-02-27  1:20 ` Brian Inglis [this message]
2018-02-27  6:12   ` Yaakov Selkowitz
2018-02-27 22:01     ` Jon Turney
2017-10-01 16:31 S. Loiseau
2017-10-01 18:54 ` Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2017-09-04  2:05 Yaakov Selkowitz

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=24d07cdb-7ad9-0ff0-65df-18502f71da72@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@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).