Re: Bug#155676: patch] dynamic sha1sums generation
On Thu, 2002-08-08 at 13:08, Jason Gunthorpe wrote:
> On Thu, 8 Aug 2002, Anthony Towns wrote:
> > But the key part of this is to have dpkg generate the md5sums at install
> > time. I suppose it'd actually be handy if you could generate the md5sums
> > just from the .deb without having to unpack it, too.
> While someone is doing this, I think it would be nice to store a proper
> filelist that has MD5, size, permissions, symlinks, major/minor and
Ok. Seems like a good idea. I'm implementing it now.
Regarding this, I'd like an opinion from the crowd: how should this
database treat conffiles? Should dpkg --verify print if they've been
changed? My initial thought was "no", and that's the way my sha1sums
patch works, but I'm curious what people think.
Also, my current plan is just to subvert the .list file into doing what
I want, by separating the values like filenames and modes with null
characters. So we'll need a way to distinguish old and new databases;
what I plan to do is add a file /var/lib/dpkg/version2-stamp or
something, and on startup dpkg will look for this file. If it exists,
it just assumes that the .list files are in the new format. If it
doesn't exist, then dpkg will convert all of the existing .list files,
and create that file. Sound good?