public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] More reliable hiding preserved libraries
Date: Mon, 5 Apr 2010 11:09:24 -0700	[thread overview]
Message-ID: <20100405180924.GA31272@hrair> (raw)
In-Reply-To: <1270474054.30670.4.camel@localhost>

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

On Mon, Apr 05, 2010 at 03:27:34PM +0200, Tiziano MMMller wrote:
> > Via that, the resolver can see that a rebuild is necessary and plan a 
> > rebuild of all consumers (whether NEEDED based or revdep).  Note 
> > preserve-lib would be rather useful here- specifically holding onto 
> > the intermediate lib while doing rebuilding.
>
> No, it doesn't help since you may have the same problems some people try
> to solve in this thread.

Might I suggest in the future purning down what you're responding to, 
to just that blurb?  At first read of your response I thought you were 
arguing against the ABI var itself (which didn't make a helluva lot of 
sense).

Meanwhile, yes, using preserve lib there still has some issues- the 
reason I mentioned it possibly being held onto is that if we're 
talking about something like openssl, having your system be horked for 
the intervening period isn't a great thing thus it may be useful as an 
option at the least.

> >   This however breaks down 
> > a bit when the ABI change is in reverse of normal versioning.
> How so? Such a var should just specify the ABI and the PM only has to
> check whether it changed from one PVR to the other. The "how" is
> completely irrelevant.

That comment is in reference to if preserve-lib is still enabled for 
the rebuild.

~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-04-05 18:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 10:38 [gentoo-dev] [RFC] More reliable hiding preserved libraries Maciej Mrozowski
2010-04-03 10:46 ` Brian Harring
2010-04-03 10:56 ` Fabian Groffen
2010-04-03 12:09   ` Maciej Mrozowski
2010-04-03 12:16     ` Fabian Groffen
2010-04-03 11:13 ` Michał Górny
2010-04-03 11:33 ` Gilles Dartiguelongue
2010-04-03 18:51 ` Tiziano Müller
2010-04-03 21:05   ` Maciej Mrozowski
2010-04-04 15:33     ` Tiziano Müller
2010-04-05  6:16       ` Maciej Mrozowski
2010-04-05  6:44         ` Brian Harring
2010-04-05 13:27           ` Tiziano Müller
2010-04-05 18:09             ` Brian Harring [this message]
2010-04-05 13:38         ` Tiziano Müller

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=20100405180924.GA31272@hrair \
    --to=ferringb@gmail.com \
    --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