Re: detailed lists with archive contents - more than just Contents
- To: debian-devel@lists.debian.org
- Subject: Re: detailed lists with archive contents - more than just Contents
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Mon, 13 May 2013 11:48:06 +0200
- Message-id: <[🔎] 20130513094805.GC8366@frosties>
- In-reply-to: <20130416190906.GA7701@alf.mars>
- References: <51262258.6000503@debian.org> <CAKTje6HawRwv+QJowSTx1OqtAgmm9RyDcSX0Vq+3-jwDShbbNw@mail.gmail.com> <CAKTje6Fjkr=8FVK9zpSmjTJp2u8UZAdUpTn9AXdkevXc2Ww4zA@mail.gmail.com> <20130416130420.GB21076@frosties> <20130416190906.GA7701@alf.mars>
On Tue, Apr 16, 2013 at 09:09:06PM +0200, Helmut Grohne wrote:
> On Tue, Apr 16, 2013 at 03:04:20PM +0200, Goswin von Brederlow wrote:
> > Will that also detect files in multiarch packages that are not identical?
>
> No, it does not do this at the moment. The main reason here is that
> currently only amd64 is processed. Support for multiple architectures
> would take a bit more to implement and vastly more resources on the
> machine hosting dedup.d.n.
>
> > Or files in foo_arch.deb that should be in foo-common_all.deb?
>
> I do not yet understand what kind of algorithm you imagine here. In any
> case dedup.d.n does not do such a thing at the moment. In addition a
> task that operates one one binary package is likely better suited for
> lintian.
>
> Helmut
Both cases would need data for multiple archs.
For the second case if identical files are in all foo_arch.deb then
those should be in foo-common_all.deb. A dedup across archs instead of
across packages.
MfG
Goswin
Reply to: