From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: zmedico@gentoo.org
Subject: [gentoo-dev] Re: adding a modification timestamp to the installed pkgs database (vdb)
Date: Tue, 27 Oct 2009 22:11:57 -0700 [thread overview]
Message-ID: <20091028051157.GA7190@hrair.hsd1.ca.comcast.net> (raw)
In-Reply-To: <4AE73CBE.8010704@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Tue, Oct 27, 2009 at 11:32:30AM -0700, Zac Medico wrote:
> Brian Harring wrote:
> > The proposal is pretty simple; if code modifies the vdb in any
> > fashion, it needs to update the mtime on a file named
> > '.modification_time' in the root of the vdb.
>
> I'd to prefer using the mtime of the /var/db/pkg directory itself,
> since existence of a '.modification_time' file isn't going to prove
> that an programs that don't recognize that file haven't made any
> modifications.
Grumble. Works for me.
> We can also use the mtimes of category subdirectories, in order to
> indicate whether a modification has occurred in any given category.
Pkgcore already relies on that for old style virtuals cache. The
pisser there is that modifications w/in a node don't result in a
category level mtime- it certainly would be nice to have it formalized
in some fashion so that cache regeneration could just work on the
areas it needs to.
~brian
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-28 5:12 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 [this message]
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
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=20091028051157.GA7190@hrair.hsd1.ca.comcast.net \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=zmedico@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