From: Vaeth <vaeth@mathematik.uni-wuerzburg.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] LibGL.la removal news item for =eselect-opengl-1.1.1-r2 going stable
Date: Sun, 17 Jan 2010 18:57:42 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.1001171845300.25920@wmax001.mathematik.uni-wuerzburg.de> (raw)
In-Reply-To: <e3BNL-ey-5@gated-at.bofh.it>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1051 bytes --]
On Sun, 17 Jan 2010, "Paweł Hajdan, Jr." wrote:
> I wonder why the affected package (eselect-opengl) couldn't run
> lafilefixer itself. It's mandatory for all users, and would save a lot
> of frustration.
It is not mandatory: You could as well re-emerge the affected packages
(shown by revdep-rebuild) which is a much cleaner solution, since it
does not break the portage database like lafilefixer does.
(Yes, I know that this might involve manual fixing the order shown
by revdep-rebuild or emerging packages twice or packages not listed,
but it *is* possible to do it cleanly).
> And I think we're doing something similar with gcc (fix_libtool_files.sh
> seems to run automatically on gcc upgrade).
Yes, this is terrible: I actually considered filing a bug about it,
requesting to make it at least only optional.
Please: When you run tools which break checksums/dates of the database,
give the user the possibility to decide whether he really wants this.
For instance, USE="+lafilefixer" might be such an option.
Martin
next parent reply other threads:[~2010-01-17 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e3Buq-8eT-1@gated-at.bofh.it>
[not found] ` <e3BNL-ey-5@gated-at.bofh.it>
2010-01-17 17:57 ` Vaeth [this message]
2010-01-17 18:20 ` [gentoo-dev] LibGL.la removal news item for =eselect-opengl-1.1.1-r2 going stable "Paweł Hajdan, Jr."
2010-01-17 18:28 ` Krzysiek Pawlik
2010-01-17 18:45 ` "Paweł Hajdan, Jr."
2010-01-17 19:09 ` Max Arnold
2010-01-25 11:39 ` Daniel Pielmeier
2010-01-17 11:26 Tomáš Chvátal
2010-01-17 11:41 ` "Paweł Hajdan, Jr."
2010-01-17 12:37 ` Ben de Groot
2010-01-24 14:01 ` Gilles Dartiguelongue
2010-01-17 11:54 ` Petteri Räty
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=Pine.LNX.4.64.1001171845300.25920@wmax001.mathematik.uni-wuerzburg.de \
--to=vaeth@mathematik.uni-wuerzburg.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