From: Tobias Klausmann <klausman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] adding a modification timestamp to the installed pkgs database (vdb)
Date: Sun, 17 Jan 2010 10:24:12 +0100 [thread overview]
Message-ID: <20100117092411.GA800@eric.schwarzvogel.de> (raw)
In-Reply-To: <20100117085914.4774f9fa@snowmobile>
Hi!
On Sun, 17 Jan 2010, Ciaran McCreesh wrote:
> > 1) portage/pkgcore support the PMS defined vdb2 while paludis doesn't
> > 2) portage/pkgcore are invoked modifying the livefs; vdb1, vdb2 is
> > updated.
> > 3) paludis is invoked. vdb1 is updated, vdb2 is not
> > 4) portage and pkgcore now cannot rely upon vdb2, since vdb1 now
> > contains extra modifications due to paludis not supporting vdb2.
>
> No, we'd not do it that way. If we're ditching VDB, the only sane way
> to do it is to ditch it with an rm -fr when creating the new layout.
> Keeping two sets of data around is going to lead to breakage no matter
> how well we do things.
Please also provide a downgrade path, i.e. a way to go back from
the new DB version to the current one should it be necessary (if
there is no such path, Murphy will see to it that the new format
breaks in interesting[0] ways).
Just my 0.0139304869 Euros (at current exchange rate),
Tobias
[0] Chinese-style interesting
--
printk("whoops, seeking 0\n");
linux-2.6.6/drivers/block/swim3.c
next prev parent reply other threads:[~2010-01-17 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 1:50 [gentoo-dev] adding a modification timestamp to the installed pkgs database (vdb) Brian Harring
2009-10-27 18:32 ` [gentoo-dev] " Zac Medico
2009-10-28 5:11 ` Brian Harring
2010-01-11 22:35 ` [gentoo-dev] " Denis Dupeyron
2010-01-12 10:12 ` Ciaran McCreesh
2010-01-12 23:12 ` Brian Harring
2010-01-17 8:59 ` Ciaran McCreesh
2010-01-17 9:24 ` Tobias Klausmann [this message]
2010-01-17 9:46 ` Ciaran McCreesh
2010-01-17 10:48 ` [gentoo-dev] " Christian Faulhammer
2010-01-17 11:09 ` Ciaran McCreesh
2010-01-18 15:42 ` Brian Harring
2010-01-18 16:37 ` Ciaran McCreesh
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=20100117092411.GA800@eric.schwarzvogel.de \
--to=klausman@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