public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem
Date: Tue, 20 Sep 2011 15:25:28 +0200	[thread overview]
Message-ID: <1316525128.1711.4.camel@belkin4> (raw)
In-Reply-To: <20110920151614.616c573c@pomiocik.lan>

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

El mar, 20-09-2011 a las 15:16 +0200, Michał Górny escribió:
> On Tue, 20 Sep 2011 15:09:01 +0200
> Pacho Ramos <pacho@gentoo.org> wrote:
> 
> > I haven't ever tried it but, what would occur if that people with
> > really updated systems simply unpack an updated stage3 tarball in
> > their / and, later, try to update?
> 
> Possibly at least few file collisions, if portage would be able to
> clean the initial mess up.
> 
> But maybe a solution is to fork a minimalistic installer/updater from
> portage which would have really tiny needs, unpack stage3 like you
> suggested and then clean up remaining files from replaced packages.
> 

Maybe we could tell that people to temporally disable protect-owned
FEATURE until update ends :-|

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

  reply	other threads:[~2011-09-20 13:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 22:14 [gentoo-dev] RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem Alex Alexander
2011-09-19 22:53 ` [gentoo-dev] " Duncan
2011-09-20  0:46   ` Rich Freeman
2011-09-20  1:44     ` Duncan
2011-09-20  7:12     ` Alex Alexander
2011-09-20 10:43       ` Patrick Lauer
2011-09-20 10:28     ` Brian Harring
2011-09-20 10:40       ` Ciaran McCreesh
2011-09-20 11:07         ` Brian Harring
2011-09-20 11:27           ` Ciaran McCreesh
2011-09-20 13:33         ` Ulrich Mueller
2011-09-20 10:50       ` Dirkjan Ochtman
2011-09-20  6:56   ` Alex Alexander
2011-09-20 13:09 ` [gentoo-dev] " Pacho Ramos
2011-09-20 13:16   ` Pacho Ramos
2011-09-20 13:16   ` Michał Górny
2011-09-20 13:25     ` Pacho Ramos [this message]
2011-09-20 13:57   ` [gentoo-dev] " Duncan
2011-09-20 14:23     ` Pacho Ramos
2011-09-20 17:00   ` [gentoo-dev] " Patrick Lauer
2011-09-21  4:00     ` [gentoo-dev] " Duncan
2011-09-21 13:24       ` Pacho Ramos
2011-09-20 15:19 ` [gentoo-dev] " Zac Medico
2011-09-20 15:28   ` Zac Medico
2011-09-20 17:03   ` Patrick Lauer
2011-09-20 17:14     ` Rich Freeman
2011-09-20 17:48       ` Alec Warner
2011-09-20 20:03         ` 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=1316525128.1711.4.camel@belkin4 \
    --to=pacho@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