public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Köhler" <skoehler@upb.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: why? pciutils with zlib use-flag went stable on   x86
Date: Sun, 29 Jul 2007 19:53:07 +0200	[thread overview]
Message-ID: <f8ik6q$5ep$1@sea.gmane.org> (raw)
In-Reply-To: <1185728016.3184.10.camel@localhost>

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

>> 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.

I'm not even complaining about that.

I will get a message, that i have to edit /etc/portage/package.use. So i
do that, and after that i'm happy and everything compiles.


But now, x86 users out there, will upgrade pciutils. They will not get
any message about the breakage. They will not realize what's wrong.

The hal-maintainers did their job: they checked, whether the zlib
use-flag is set properly for pciutils. But this check is not executed,
since hal has not been revbumbed on x86.

And the pciutils-maintainers? They should check, where hal is installed
- or maybe they should simply check the hal use-flag.
And then, they should output a message, that the zlib use-flag would
actually do harm. But the ebuild doesn't do that.



So i think, right now, during these hours, clueless x86 gentoo users
will upgrade their pciutils, not even realizing, that should do that
with disabled zlib use-flag.


I'm becoming a little sarcastic, but i hope, the problems with
disharmony causes, will be noticed soon by others.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-07-29 17: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
2007-07-29 17:53   ` Sven Köhler [this message]
2007-07-29 17:27 ` 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='f8ik6q$5ep$1@sea.gmane.org' \
    --to=skoehler@upb.de \
    --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