All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, Laszlo Ersek <lersek@redhat.com>,
	qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	qemu-trivial@nongnu.org,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] configure: Check bzip2 is available
Date: Fri, 8 Nov 2019 18:07:27 +0100	[thread overview]
Message-ID: <51f9b2d9-b196-c30e-dc67-988e29b5df47@redhat.com> (raw)
In-Reply-To: <00cca0a5-7a51-f2d1-5120-821c335954b8@redhat.com>

On 11/8/19 4:43 PM, Eric Blake wrote:
> On 11/8/19 5:01 AM, Laszlo Ersek wrote:
> 
>>>
>>> Add a check in ./configure to warn the user if bzip2 is missing.
>>
>> We've come full circle. Let me explain:
>>
>>>
>>> Fixes: 536d2173b2b
>>
>> So this makes me kinda grumpy. If you look at the v3 posting of the 
>> patch that would later become commit 536d2173b2b:
>>
>>    http://mid.mail-archive.com/20190321113408.19929-8-lersek@redhat.com
>>
>> you see the following note in the changelog:
>>
>>      - compress FD files with bzip2 rather than xz, so that 
>> decompression at
>>        "make install" time succeed on older build OSes too [Peter]
>>
>> So I couldn't use xz because that was "too new" for some build OSes, 
>> but now we also can't take bzip2 for granted because that's "too old" 
>> for some other build OSes? This is ridiculous.
>>
>> To be clear, my disagreement is only with the "Fixes" tag. For me, 
>> "Fixes" stands for something that, in retrospect, can be proven to 
>> have been a bug at the time the code was *originally* committed. But, 
>> at the time, taking "bzip2" for granted was *not* a bug. The 
>> conditions / circumstances have changed more recently, and the 
>> assumption about bzip2 has been invalidated *after* adding a 
>> dependency on bzip2.
>>
>> Nonetheless, thank you for adapting the code to the potential absence 
>> of bzip2. Can you perhaps go in some details in the commit message, 
>> near "not included in default installations" and "freshly installed 
>> systems"? If we can, we should identify the exact distro release where 
>> this problem has been encountered (and I wouldn't mind a link to the 
>> BZ or ticket under which people agreed to remove bzip2 from the 
>> default package set).
> 
> 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.


  reply	other threads:[~2019-11-08 17:09 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é [this message]
2019-11-08 17:10       ` Peter Maydell
2019-11-11 11:51         ` Thomas Huth
2019-11-11 13:33           ` Aleksandar Markovic

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=51f9b2d9-b196-c30e-dc67-988e29b5df47@redhat.com \
    --to=philmd@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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.