From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC about another *DEPEND variable
Date: Sun, 24 Sep 2006 03:36:21 +0100 [thread overview]
Message-ID: <20060924033621.32c44881@snowdrop.home> (raw)
In-Reply-To: <200609211101.41237.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Thu, 21 Sep 2006 11:01:40 -0400 Mike Frysinger <vapier@gentoo.org>
wrote:
| On Thursday 21 September 2006 10:54, Donnie Berkholz wrote:
| > Yes, I agree with you. For example, take expat. The maintainers have
| > refused to allow both versions to exist simultaneously on a system
| > because it apparently causes more breakage than just breaking every
| > app on your system by removing .so.0.
|
| that is the exact case portage should be handling for you
|
| it would go "oh hey, check out libexpat.so.0 ... some things seem to
| want it ... HEY USER, you need to rebuild: xxxxxxxx" ... once all the
| packages still consuming libexpat.so.0 are rebuilt, portage could
| silently trim it from the system
|
| complicated ? not really, scanelf can produce all this information
| in an easily digestable format
How would it know what other files are required? For example, if
libexpat.so.0 were to rely upon /usr/share/expat-0/config , how would
the package manager know not to clobber that file? Or are you
suggesting leaving (or reparenting, if you prefer) all a package's
files, not just the .so files?
Or a related question: what proportion of breakages will be fixed
merely by keeping .so files and nothing else around? Will implementing
this prevent enough breakages to make it worthwhile?
--
Ciaran McCreesh
Mail : ciaranm at ciaranm.org
Web : http://ciaranm.org/
as-needed is broken : http://ciaranm.org/show_post.pl?post_id=13
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-24 2:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 10:35 [gentoo-dev] RFC about another *DEPEND variable Alin Nastac
2006-09-21 11:38 ` Luca Barbato
2006-09-21 11:59 ` Brian Harring
2006-09-21 13:52 ` Mike Frysinger
2006-09-21 14:04 ` Brian Harring
2006-09-21 14:43 ` Mike Frysinger
2006-09-21 15:08 ` Brian Harring
2006-09-23 10:20 ` Mike Frysinger
2006-09-23 13:14 ` Brian Harring
2006-09-23 13:50 ` Mike Frysinger
2006-09-23 13:59 ` Mike Frysinger
2006-09-23 14:30 ` Brian Harring
2006-09-24 3:31 ` Mike Frysinger
2006-09-25 18:16 ` Brian Harring
2006-09-27 6:24 ` Mike Frysinger
2006-09-27 7:54 ` Brian Harring
2006-09-30 18:01 ` Mike Frysinger
2006-09-30 19:34 ` Brian Harring
2006-10-02 12:53 ` Mike Frysinger
2006-09-21 14:14 ` Donnie Berkholz
2006-09-21 14:40 ` Mike Frysinger
2006-09-21 14:54 ` Donnie Berkholz
2006-09-21 15:01 ` Mike Frysinger
2006-09-24 2:36 ` Ciaran McCreesh [this message]
2006-09-24 3:13 ` Mike Frysinger
2006-09-21 14:56 ` Duncan Coutts
2006-09-21 15:10 ` Simon Stelling
2006-09-21 15:11 ` Mike Frysinger
2006-09-21 15:41 ` Duncan Coutts
2006-09-21 18:27 ` Luca Barbato
2006-09-21 21:34 ` Duncan Coutts
2006-09-21 23:25 ` Luca Barbato
2006-09-23 10:13 ` Mike Frysinger
2006-09-23 10:35 ` Duncan Coutts
2006-09-23 10:52 ` Mike Frysinger
2006-09-21 14:38 ` Alin Nastac
2006-09-21 14:46 ` Mike Frysinger
2006-09-21 17:24 ` Alin Nastac
2006-09-21 14:51 ` Brian Harring
2006-09-21 17:15 ` Alin Nastac
2006-09-21 19:51 ` Brian Harring
2006-09-23 10:05 ` Mike Frysinger
2006-09-23 14:24 ` Alin Nastac
2006-09-23 14:34 ` Mike Frysinger
2006-09-23 14:53 ` Brian Harring
2006-09-23 15:07 ` Mike Frysinger
2006-09-21 12:05 ` Alin Nastac
2006-09-21 13:50 ` Mike Frysinger
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=20060924033621.32c44881@snowdrop.home \
--to=ciaranm@ciaranm.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