All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"QEMU Trivial" <qemu-trivial@nongnu.org>,
	"Laszlo Ersek" <lersek@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] configure: Check bzip2 is available
Date: Mon, 11 Nov 2019 14:33:39 +0100	[thread overview]
Message-ID: <CAL1e-=jOcLGdMM0vzdCxXHuu3cBp=VX9vkaxp7GPQZQtTF52FQ@mail.gmail.com> (raw)
In-Reply-To: <ac065856-56e2-bceb-851c-a9c150068e71@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

On Monday, November 11, 2019, Thomas Huth <thuth@redhat.com> wrote:

> On 08/11/2019 18.10, Peter Maydell wrote:
> > On Fri, 8 Nov 2019 at 17:07, Philippe Mathieu-Daudé <philmd@redhat.com>
> wrote:
> >> On 11/8/19 4:43 PM, Eric Blake wrote:
> >>> bzip2 is no longer a favored compression.  If we are trying to pick a
> >>> compression that is most likely to be present on any system, go with
> >>> gzip.  If we are trying to pick a compression that packs tighter and
> >>> uncompresses faster, pick xz or zstd.  But bzip2 does neither: it packs
> >>> slightly tighter than gzip but has slower performance in doing so, and
> >>> thus is no longer used as a default compression.
> >>
> >> The problem was with OpenBSD 6.1 which hadn't xz available.
> >>
> >> In commit 12745eaa02 Gerd updated the VM to OpenBSD 6.5 and we now have
> >> access to xz. IIRC OSX supported versions also provide xz.
> >>
> >> If we want to revert Laszlo's patches and apply his first version (using
> >> xz), we should do that during 5.0 dev cycle, now it is too late.
> >> I'd prefer we simply fix bzip2 for the next release.
> >
> > I don't think we should try to use 'xz' because I don't see
> > the point. We should use something that's generally available,
> > whether that's bzip2 or gzip. Life's too short to deal with
> > yet another file compression tool and format.
>
> FWIW, on the weekend, I accidentially came accross this page:
>
>  https://www.nongnu.org/lzip/xz_inadequate.html
>
> After reading that, I also don't think anymore that we should switch to
> 'xz'.



Off topic, but, from the page you linked to:

There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.
-- C.A.R. Hoare

Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away.
-- Antoine de Saint-Exupery

Perhaps we should display these quotes at some highly visible place on our
dev QEMU website. ;)

Aleksandar



>
>  Thomas
>
>
>

[-- Attachment #2: Type: text/html, Size: 3184 bytes --]

      reply	other threads:[~2019-11-11 13:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 10:28 [PATCH] configure: Check bzip2 is available Philippe Mathieu-Daudé
2019-11-08 10:31 ` Daniel P. Berrangé
2019-11-08 10:34 ` Thomas Huth
2019-11-08 10:42   ` Philippe Mathieu-Daudé
2019-11-08 11:39     ` Laszlo Ersek
2019-11-08 11:58       ` Philippe Mathieu-Daudé
2019-11-08 12:03       ` Thomas Huth
2019-11-08 11:01 ` Laszlo Ersek
2019-11-08 11:05   ` Daniel P. Berrangé
2019-11-08 11:54   ` Philippe Mathieu-Daudé
2019-11-08 11:57     ` Thomas Huth
2019-11-08 15:43   ` Eric Blake
2019-11-08 17:07     ` Philippe Mathieu-Daudé
2019-11-08 17:10       ` Peter Maydell
2019-11-11 11:51         ` Thomas Huth
2019-11-11 13:33           ` Aleksandar Markovic [this message]

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='CAL1e-=jOcLGdMM0vzdCxXHuu3cBp=VX9vkaxp7GPQZQtTF52FQ@mail.gmail.com' \
    --to=aleksandar.m.mail@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.