public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-portage-dev] About how to make compilation think some files are missing
@ 2011-02-12 15:50 Pacho Ramos
  2011-02-12 17:22 ` Martin Doucha
  2011-02-12 23:43 ` Zac Medico
  0 siblings, 2 replies; 6+ messages in thread
From: Pacho Ramos @ 2011-02-12 15:50 UTC (permalink / raw
  To: gentoo-portage-dev

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

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

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

^ permalink raw reply	[flat|nested] 6+ messages in thread
* [gentoo-portage-dev] About how to make compilation think some files are missing
@ 2011-02-12 16:06 Pacho Ramos
  0 siblings, 0 replies; 6+ messages in thread
From: Pacho Ramos @ 2011-02-12 16:06 UTC (permalink / raw
  To: gentoo-portage-dev

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

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


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-02-13 12:06 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
  -- strict thread matches above, loose matches on Subject: below --
2011-02-12 16:06 Pacho Ramos

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox