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] Re: adding a modification timestamp to the installed  pkgs database (vdb)
Date: Sun, 17 Jan 2010 11:09:07 +0000	[thread overview]
Message-ID: <82dd739f1001170309m5dc6b20cm8379b23fc70e8d67@mail.gmail.com> (raw)
In-Reply-To: <20100117114849.09ddb5b3@gentoo.org>

2010/1/17 Christian Faulhammer <fauli@gentoo.org>:
> Ciaran McCreesh <ciaran.mccreesh@googlemail.com>:
>  As much as you love to have the new and shiny VDB2, it is far off.
> Prototyping and drafting implementations would be great to have some
> base where we can discuss on (in a civil manner).  So having this
> timestamp would be a good way to prepare a sane migration path.

No, it wouldn't. Brian's proposal a) would be of no use whatsoever for
VDB2 migration, and b) would not be used by VDB2. Having a *decent*
cache validation mechanism is a good idea; having a half-baked one is
a waste of time.

-- 
Ciaran McCreesh



  reply	other threads:[~2010-01-17 11:09 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
2010-01-17  9:46           ` Ciaran McCreesh
2010-01-17 10:48             ` [gentoo-dev] " Christian Faulhammer
2010-01-17 11:09               ` Ciaran McCreesh [this message]
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=82dd739f1001170309m5dc6b20cm8379b23fc70e8d67@mail.gmail.com \
    --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