From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: why? pciutils with zlib use-flag went stable on x86
Date: Thu, 02 Aug 2007 14:15:19 +0100 [thread overview]
Message-ID: <f8slcv$9e2$1@sea.gmane.org> (raw)
In-Reply-To: m3ir7yqg4c.fsf_-_@lugabout.jhcloos.org
James Cloos wrote:
> The pciutils ebuild should be re-engineered to use separate USE flags
> for linking to libz and compressing the database.
++
It may be what upstream (pciutils) do by default, but no other distro ships
with compressed ids for the reasons you outline (and you can't mmap the
file). It breaks a default desktop installation (aiui) so it really
shouldn't use a default system-wide USE flag, but a local one. Anyone who
really wants it can set it, and everyone else's machines will still work.
As Mr Gianelloni spelt out on bugzilla[1]:
"when you install from stage3, then immediately type "emerge [blah]", I
would expect it to work. If it does not, then it is a failure in the
ebuild and a bug... it is your responsility to ensure that your package is
not broken with a default installation."
I don't know if that's policy or not, but imo it should be.
On a wider note, it seemed to me from the bug to be more of a dispute
between HAL upstream and pciutils upstream. I wonder how many such disputes
are actually resolved within Gentoo, since it seems the kind of thing that
would show up most in a source distro.
(And as such shows another reason why Gentoo is so important to the wider
community. Certainly devs from other projects i've met on IRC who use
Gentoo seem a lot less stressed than those on other distros.. ;)
[1] http://bugs.gentoo.org/show_bug.cgi?id=120088#c3
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-08-02 13:18 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 ` [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 [this message]
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='f8slcv$9e2$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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