public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
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 19:45:00 +0100	[thread overview]
Message-ID: <4B535AAC.50406@gentoo.org> (raw)
In-Reply-To: <4B5356B7.6090802@gentoo.org>

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

On 1/17/10 7:28 PM, Krzysiek Pawlik wrote:
> On 01/17/10 18:20, "Paweł Hajdan, Jr." wrote:
>>> Please: When you run tools which break checksums/dates of the database,
>>> give the user the possibility to decide whether he really wants this.
>> Good point, I didn't realize that. However, I'd rather fix the tool (for
>> example to update the portage database).
> Nope, that's a bad idea unless you plan to implement such feature for portage,
> paludis and pkgcore (and possibly other package managers).
> So use revdep-rebuild (longer but correct solution) or lafilefixer (quicker but
> introduces other problems).

Hmm... last time I tried revdep-rebuild for that problem it either
didn't notice something was wrong, or couldn't finish without manual
assistance.

How about fixing lafilefixer in an other way: it knows which .la files
are broken. Instead of changing their contents, it can re-emerge the
packages they belong to. But then it probably can't be run automatically
by the ebuild (nested emerges).

On the other hand, I really wonder how useful the checksums in portage
db really are. It includes config files which are frequently modified.
It also doesn't include config files the administrator has to create. So
for example for verifying system integrity is seems useless to me.

I'd expect only a limited group of users caring about the checksum
database, and the majority of affected users caring about the update to
"just work" (which running lafilefixer --just-fixit automatically would
buy us).

Paweł Hajdan jr


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

  reply	other threads:[~2010-01-17 18:45 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   ` [gentoo-dev] LibGL.la removal news item for =eselect-opengl-1.1.1-r2 going stable Vaeth
2010-01-17 18:20     ` "Paweł Hajdan, Jr."
2010-01-17 18:28       ` Krzysiek Pawlik
2010-01-17 18:45         ` "Paweł Hajdan, Jr." [this message]
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=4B535AAC.50406@gentoo.org \
    --to=phajdan.jr@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