On Mon, May 13, 2013 at 11:48:06AM +0200, Goswin von Brederlow wrote: > 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.
Thanks for explaining. Still this task is quite different from the task dedup.d.n is solving, since it requires to look at one package instead of looking at one architecture (+ all). Adding support for this to dedup.d.n would vastly increase resource usage beyond the currently available hardware. In addition the scalability issues differ, since the number of architectures is comparatively small to the number of packages. Maybe a different tool can solve these two useful tasks you proposed? Helmut -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130513132135.ga28...@alf.mars
