Re: dpkg

[Ben Collins <bcollins@debian.org>]

On Fri, Mar 30, 2001 at 06:23:05AM -0800, Joey Hess wrote:
> Ben Collins wrote:
> > As it reads, it is allocating memory for, and creating a very large in
> > memory structure. I think it also verifies the files associated with the
> > package, and does some other sanity checks.
> 
> It's not looking at any other files according to strace.

Somewhere down the line, it reads all of the .files

> > IMO, about the only way to
> > get real speedup is for all of this data to be in a hashed database,
> > on disk, so all dpkg has to do is open the database and verify files.
> > The hash will already be avaiable. However, there are probably some
> > caveats to this.
> 
> Well another useful optimization would be to not read the available file
> at all if nothing it is going to do involves the available file.
> 
> I've just zeroed mine out, sigh.

Some of the installs change what is in the available file. However, we
do need to get rid of it somehow. Dselect holds us back again...

Wichert, any plans on how to deintegrate dselect from dpkg? Maybe a
dpkg-available tool that dpkg can start calling when it needs to?

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'