public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] About how to make compilation think some files are missing
Date: Sun, 13 Feb 2011 12:54:26 +0100	[thread overview]
Message-ID: <1297598066.17011.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4D571B19.3010800@gentoo.org>

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

El sáb, 12-02-2011 a las 15:43 -0800, Zac Medico escribió:
> On 02/12/2011 07:50 AM, Pacho Ramos wrote:
> > This comes from glitz removal (bug #330397), as soon as cairo-1.10 gets
> > stabilized, depclean will try to remove glitz, but removing glitz will
> > break a lot of apps, needing to rebuild them and, until then, having a
> > partially broken system.
> > 
> > I then thought on running revdep-rebuild --library libglitz-glx.so.1
> > BEFORE removing glitz (to prevent breakage), but later I remembered it
> > wouldn't work as rebuilt packages would link again against
> > libglitz-glx.so.1.
> > 
> > Then, my idea would the following:
> > 
> > Would be nice if I could tell portage to make compilation think
> > libglitz-glx.so.1 is not present in real system (maybe sandbox could
> > prevent its readability inside build environment), and then, I could run
> > "revdep-rebuild --library libglitz-glx.so.1" before removing glitz and
> > affected apps would not link to it, allowing me to safely remove glitz
> > later without having had  a broken system at any time.
> > 
> > What do you think? Thanks
> 
> Ideally, the build system(s) involved would have options to explicitly
> disable linking against the deprecated library.
> 
> Barring that possibility, something like your sandbox idea seems like
> the second-best solution.
> 
> On par with the the sandbox idea would be to migrate the deprecated
> library to a directory which is not included in the default library
> search path, and to use a global LD_LIBRARY_PATH setting so that your
> apps can find it until they are rebuilt. Then you could execute your
> rebuilds in an environment with a modified LD_LIBRARY_PATH value that
> excludes the path of the deprecated library.

Didn't think about that last LD_LIBRARY_PATH option, looks easier for
now. Thanks

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-02-13 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-12 15:50 [gentoo-portage-dev] About how to make compilation think some files are missing Pacho Ramos
2011-02-12 17:22 ` Martin Doucha
2011-02-12 18:57   ` Pacho Ramos
2011-02-12 23:43 ` Zac Medico
2011-02-13 11:54   ` Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-12 16:06 Pacho Ramos

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=1297598066.17011.1.camel@localhost.localdomain \
    --to=pacho@gentoo.org \
    --cc=gentoo-portage-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