Bug#944968: popularity-contest: Program accesses internal dpkg database
- To: Bill Allombert <ballombe@debian.org>
- Cc: Niels Thykier <niels@thykier.net>, 944968@bugs.debian.org
- Subject: Bug#944968: popularity-contest: Program accesses internal dpkg database
- From: Guillem Jover <guillem@debian.org>
- Date: Sat, 1 Feb 2020 19:02:38 +0100
- Message-id: <[🔎] 20200201180238.GA3814@gaara.hadrons.org>
- Reply-to: Guillem Jover <guillem@debian.org>, 944968@bugs.debian.org
- In-reply-to: <20191128214144.fdaiq5h2fj5avknb@yellowpig>
- References: <20191117214402.GF30024@gaara.hadrons.org> <20191117215958.cr5uyja7gb3tapse@yellowpig> <7617df59-5ac7-31da-1895-1126681a7129@thykier.net> <20191119083457.GB138745@thunder.hadrons.org> <20191119102756.a2i4jegdr4uzecj7@yellowpig> <20191119102756.a2i4jegdr4uzecj7@yellowpig> <c4bcf90a-0c9b-e278-2658-420479a11ca9@thykier.net> <20191128214144.fdaiq5h2fj5avknb@yellowpig> <20191117214402.GF30024@gaara.hadrons.org>
On Thu, 2019-11-28 at 22:41:44 +0100, Bill Allombert wrote:
> On Thu, Nov 28, 2019 at 08:55:00PM +0000, Niels Thykier wrote:
> > While it would take a bit of restructuring / refactoring, I think it
> > would be possible to use a single dpkg-query for everything and still be
> > able to process the data in a "streaming" fashion.
>
> Yes this could work, however this is assuming that dpkg-query is not
> allocating everything in memory at once.
dpkg-query will load everything in memory, in the same way it does
while doing a «dpkg --install» or similar. The key here is that these
files are just going to disappear in an inminent future, and anything
relying on them will just break. Also dpkg will be moving into keeping
the entire package filesystem knowledge in a single database file anyway.
Thanks,
Guillem
Reply to: