From: "Alon Bar-Lev" <alonbl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] gnupg-2 stable plans
Date: Wed, 12 Dec 2007 07:10:02 +0200 [thread overview]
Message-ID: <9e0cf0bf0712112110p2b7ab810r6e8a026b07822271@mail.gmail.com> (raw)
In-Reply-To: <20071211231404.GI31432@supernova>
On 12/12/07, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> On 22:49 Tue 11 Dec , Alon Bar-Lev wrote:
> > On Dec 9, 2007 9:21 AM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > > On 15:49 Sat 08 Dec , Alon Bar-Lev wrote:
> > > Seems reasonable. Any particular reason to slot gnupg-2 as SLOT 0 rather
> > > than SLOT 1.9?
> >
> > he end result would be one slot... If I need to chose 1.9 or 0, I prefer the
> > standard is to have slot 0.
>
> What happens to people who only have slot 1.9 installed and not slot 0,
> or vice versa? You might want to test a few different upgrade scenarios
> to see what portage does.
OK, I will try this.
> > > > 2. Perform slot-move of slot "0" and slot "1.9" into slot "2", so
> > > > migration will be smooth. The problem is that I need all archs to work
> > > > with me in timely manner so that this will be possible. I have
> > > > bug#194113 waiting for arm, mips, s390, sh, and this only for the
> > > > dependencies.
> > >
> > > I can imagine this resulting in very weird issues, when you have two of
> > > the same package installed in the same slot.
> >
> > What?
> > These are two versions....
>
> Right, but two versions are never supposed to be installed into the same
> slot. They are during upgrade/downgrade, but that's short-term. Some
> package managers could respond oddly. If you were going to go this
> route, it would again be worth testing in advance.
I don't understand... It works quite some time for many people.
Alon.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-12-12 5:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 13:49 [gentoo-dev] [RFC] gnupg-2 stable plans Alon Bar-Lev
2007-12-09 7:21 ` Donnie Berkholz
2007-12-11 20:49 ` Alon Bar-Lev
2007-12-11 23:14 ` Donnie Berkholz
2007-12-12 5:10 ` Alon Bar-Lev [this message]
2007-12-12 4:37 ` William L. Thomson Jr.
2007-12-12 5:07 ` Alon Bar-Lev
2007-12-12 9:10 ` Jan Kundrát
2007-12-12 12:26 ` Alon Bar-Lev
2007-12-12 15:08 ` William L. Thomson Jr.
2007-12-12 15:55 ` Santiago M. Mola
2007-12-12 16:11 ` Doug Klima
2007-12-12 16:51 ` William L. Thomson Jr.
2007-12-12 15:17 ` Jan Kundrát
2007-12-12 10:15 ` Mart Raudsepp
2007-12-12 12:30 ` Alon Bar-Lev
2007-12-12 15:03 ` William L. Thomson Jr.
2007-12-13 4:46 ` Robin H. Johnson
2007-12-13 5:57 ` William L. Thomson Jr.
2007-12-13 17:28 ` [gentoo-dev] " Alon Bar-Lev
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=9e0cf0bf0712112110p2b7ab810r6e8a026b07822271@mail.gmail.com \
--to=alonbl@gentoo.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