From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-05-14
Date: Wed, 1 May 2013 12:35:10 -0400 [thread overview]
Message-ID: <CAGfcS_k+nMZJw1eFUJu3g8XjthOahkU+_C7HE4AmSKUDREyyhQ@mail.gmail.com> (raw)
In-Reply-To: <20130501162247.17bc7f11@googlemail.com>
On Wed, May 1, 2013 at 11:22 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> ...and that it's utterly frickin' broken as a concept, and that
> adopting it will slow down people switching to the proper solution to
> the problem, which is slots.
Unless we fully slot (not subslot) every version of everything that
gets linked there is still the issue of what happens between the time
package A is upgraded, and package B which depends on A is upgraded.
That will often be minutes, and could be hours or days even with slot
operator dependencies. Some packages take a long time to build, and
if there is a failure it might take a user days to work it out.
Even if preserve-libs is imperfect, it improves usability. Are there
any scenarios where it actually makes things worse? Sure, maybe once
in a blue moon a lib no longer works because it is out of sync with a
config file, but would it work any better if it were just outright
deleted?
Rich
next prev parent reply other threads:[~2013-05-01 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 16:59 [gentoo-project] Call for agenda items - Council meeting 2013-05-14 Petteri Räty
2013-04-27 21:27 ` Michał Górny
2013-05-01 7:37 ` Ulrich Mueller
2013-05-01 15:15 ` Mike Gilbert
2013-05-01 15:18 ` Zac Medico
2013-05-01 15:22 ` Ciaran McCreesh
2013-05-01 15:28 ` Michał Górny
2013-05-01 15:35 ` Ciaran McCreesh
2013-05-01 17:27 ` Zac Medico
2013-05-01 17:30 ` Ciaran McCreesh
2013-05-01 17:35 ` Rich Freeman
2013-05-01 17:45 ` Ciaran McCreesh
2013-05-01 16:35 ` Rich Freeman [this message]
2013-05-01 15:39 ` Michał Górny
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=CAGfcS_k+nMZJw1eFUJu3g8XjthOahkU+_C7HE4AmSKUDREyyhQ@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-project@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