public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
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 08:59:14 +0000	[thread overview]
Message-ID: <20100117085914.4774f9fa@snowmobile> (raw)
In-Reply-To: <20100112231223.GC6656@hrair>

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

2010/1/12 Brian Harring <ferringb@gmail.com>:
>> There's no discussion because Brian refuses to address any comments
>> on the proposal and just says "we should do it anyway, and if you
>> want it done properly instead, do it yourself".
>
> This is a bit of bullshit, per the norm.  There is plenty of
> discussion- the problem is you don't like the direction it's gone.
> You want a whole new vdb- I don't oppose that.  However I'm not
> interested in trying to standardize a new vdb format into PMS, at
> least not yet.

No, I want a decent cache proposal that lets package managers know
what's changed, not one that sometimes (but not always) might let
package managers know when some things have changed, but not what's
changed and not what they can still assume.

> Your argument can basically be summed up as "don't do the minimal
> tweak, do the whole new vdb with defined caches that all can share".

No, I want the well defined caches that all can share.

> The daft thing about this is that you're ignoring one core transition
> issue w/ vdb2- if someone did create a vdb2, they still would need a
> synchronization mechanism (one quite similar to what I'm proposing).

If you replace VDB, you need a well defined cache mechanism. So let's
do that bit now.

> 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.

> Summarizing; the synchronization primitive is needed for any future
> vdb2

No. A *proper* cache validation mechanism is needed. What you're
suggesting isn't enough to use for anything at all.

> Summing it up; what ciaran wants is reliant on what I'm proposing,

No, what I want in the long term is reliant upon implementing a decent
cache setup in the short term.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-01-17  9:00 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 [this message]
2010-01-17  9:24         ` Tobias Klausmann
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=20100117085914.4774f9fa@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --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