From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] expat upgrade, kdelibs: circular problem?
Date: Wed, 19 Mar 2008 15:11:46 +0100 [thread overview]
Message-ID: <20080319141145.GA9409@nibiru.local> (raw)
In-Reply-To: <200803190858.49288.alan.mckinnon@gmail.com>
* Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Tuesday 18 March 2008, Enrico Weigelt wrote:
> > BTW: if libexpat.so.0 was there before the update and now isn't,
> > there's an major bug in expat (either the ebuild or the source).
>
> There's no bug in expat, the OP is doing an *expat*upgrade*, which
> means that libexpat.so.0 was there before and libexpat.so.1 is there
> now. Thus any app that links explicitly to libexpat.so.0 is now broken.
If an upgrade breaks primary things, it's simply broken.
You can now choose, whether the bug is expat or the ebuild/portage.
> 2. Something like revdep-rebuild that scans the system looking for
> errors and is triggered manually by the user.
This is also ugly and error-prone. After every slightest upgrade
you have to fear nothing's running anymore and everything has to be
rebuilt first. If downtimes don't matter, fine. But for critical
systems, this is very dangerous.
Why not modeling/storing the *runtime* dependencies and doing
an *clean* MVCC ? Isn't this what slotting was meant for ? ;-P
> Imagine using a binary distro where the packager didn't
> pick this up and you are left stranded with no easy way to fix it...
Then the package manager's obviously broken ...
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-19 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 8:48 [gentoo-user] expat upgrade, kdelibs: circular problem? brullo nulla
2008-03-17 9:03 ` Alan McKinnon
2008-03-17 18:29 ` brullo nulla
2008-03-17 21:25 ` Alan McKinnon
2008-03-19 1:49 ` Paul Varner
2008-03-18 18:49 ` Enrico Weigelt
2008-03-19 6:58 ` Alan McKinnon
2008-03-19 14:11 ` Enrico Weigelt [this message]
2008-03-19 19:45 ` brullo nulla
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=20080319141145.GA9409@nibiru.local \
--to=weigelt@metux.de \
--cc=gentoo-user@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