On 02/14/2010 06:26 PM, Brian Harring wrote:
> How about a more descriptive name... build_time or something similar.
> Yes, CTIME means creation time, but I'd rather not overload terms that
> have specific meanings already just for the sake of saving a few chars
> in typing the filename in...
>
On 02/14/2010 06:02 PM, Ned Ludd wrote:
>> Ok, then how about a vdb entry named CTIME that contains an integer
>> number of seconds since the unix Epoch?
>
> That would be UNIXTIME vs CTIME I'd think.
I was alluding to the stat(2) st_ctime field, but I guess BUILD_TIME
is probably more appropriat
On Sun, Feb 14, 2010 at 06:02:28PM -0800, Ned Ludd wrote:
> On Sun, 2010-02-14 at 12:11 -0800, Zac Medico wrote:
> > On 02/14/2010 04:36 AM, Brian Harring wrote:
> > > This gets nasty... you're basically talking about the rpm equivalent
> > > of EPOCH.
> > >
> > > Not a fan of an adhoc UUID (espe
On Sun, 2010-02-14 at 12:11 -0800, Zac Medico wrote:
> On 02/14/2010 04:36 AM, Brian Harring wrote:
> > This gets nasty... you're basically talking about the rpm equivalent
> > of EPOCH.
> >
> > Not a fan of an adhoc UUID (especially since it'll become standard
> > via portage doing it), but a *
On 02/14/2010 04:36 AM, Brian Harring wrote:
> This gets nasty... you're basically talking about the rpm equivalent
> of EPOCH.
>
> Not a fan of an adhoc UUID (especially since it'll become standard
> via portage doing it), but a *timestamp* for the build, labeled as
> such, gets you what you w
On Fri, Feb 12, 2010 at 04:24:05PM -0800, Zac Medico wrote:
> On 02/12/2010 01:38 PM, Brian Harring wrote:
> > On Fri, Feb 12, 2010 at 12:54:21PM -0800, Zac Medico wrote:
> >> Hi,
> >>
> >> I'm thinking about adding a UUID file in /var/db/pkg, for comparing
> >> installed packages to binary package
On 02/12/2010 01:38 PM, Brian Harring wrote:
> On Fri, Feb 12, 2010 at 12:54:21PM -0800, Zac Medico wrote:
>> Hi,
>>
>> I'm thinking about adding a UUID file in /var/db/pkg, for comparing
>> installed packages to binary packages. We already have BINPKGMD5,
>> but the problem with that is that the M
On Fri, Feb 12, 2010 at 12:54:21PM -0800, Zac Medico wrote:
> Hi,
>
> I'm thinking about adding a UUID file in /var/db/pkg, for comparing
> installed packages to binary packages. We already have BINPKGMD5,
> but the problem with that is that the MD5 of a binary package
> changes when it's updated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm thinking about adding a UUID file in /var/db/pkg, for comparing
installed packages to binary packages. We already have BINPKGMD5,
but the problem with that is that the MD5 of a binary package
changes when it's updated for package moves. A UUID
