public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  why? pciutils with zlib use-flag went stable on x86
Date: Sun, 29 Jul 2007 19:53:36 +0300	[thread overview]
Message-ID: <1185728016.3184.10.camel@localhost> (raw)
In-Reply-To: <f8ig5t$p6v$1@sea.gmane.org>

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

On P, 2007-07-29 at 18:44 +0200, Sven Köhler wrote:
> Hi,
> 
> so today, pciutils-2.2.4-r3 went stable on x86.
> It's a known issue, that pciutils compiled with zlib use-flag turned on
> (which is default) doesn't work with the version of hal, which is
> currently stable on x86.
> 
> So at the moment, hal-0.5.9-r1 is stable on x86. It went stable weeks or
> even months ago. Now, pciutils-2.2.4-r3 is compiled with zlib use-flag
> turned on. There are now warning, errors, or any other messages about
> the zlib use-flag - well, until you recompile hal.
> 
> The hal-ebuild checks, whether pciutils has been built with or without
> the zlib use-flag. But what is this check worth, if people have already
> upgraded hal weeks ago and the uncompatibility between pciutils and hal
> is now unnoticed?
> 
> 
> Why did you provocate this breakage?
> 
> 
> This is not a good idea, IMHO.

No. And many gave up getting this sensible again.
As is, the default USE flags for a desktop profile lead to a compilation
failure when unattended due to this, which is very very bad.

At one point I thought I will simply not stabilize GNOME-2.18 until
pciutils is fixed to follow what upstream wants, what most other
maintainers wish, and what is sensible to do. I see no reason whatsoever
for this gzipping, not even for embedded devices as a gzipped file can't
be mmapped.
Then I realized GNOME-2.16 compilation for a fresh system with desktop
profiles is broken now also anyhow.

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-29 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 16:44 [gentoo-dev] why? pciutils with zlib use-flag went stable on x86 Sven Köhler
2007-07-29 16:53 ` Mart Raudsepp [this message]
2007-07-29 17:53   ` [gentoo-dev] " Sven Köhler
2007-07-29 17:27 ` [gentoo-dev] " Wulf C. Krueger
2007-07-29 19:15   ` [gentoo-dev] " Ryan Hill
2007-07-29 21:01     ` Seemant Kulleen
2007-07-29 17:36 ` [gentoo-dev] " Carsten Lohrke
2007-07-29 17:45   ` Carsten Lohrke
2007-07-29 18:04     ` [gentoo-dev] " Sven Köhler
2007-07-29 18:24       ` Arfrever Frehtes Taifersar Arahesis
2007-07-29 18:46       ` Steev Klimaszewski
2007-08-02 12:23       ` James Cloos
2007-08-02 13:15         ` Steve Long
2007-08-03  1:39           ` Chris Gianelloni
2007-08-02 16:26         ` Sven Köhler
2007-08-02 23:19           ` Ryan Hill
2007-08-02 23:50             ` Robin H. Johnson
2007-08-03  0:07               ` Ryan Hill
2007-08-03  1:37         ` Chris Gianelloni

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=1185728016.3184.10.camel@localhost \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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