Le 30/05/2019 à 04:14, Paul Wise a écrit : > dak needs a way to restrict the availability of arch:all packages to > certain architecture's Packages files. This would also be useful for > interpreted code that only has support for certain kernel interfaces > that aren't available on non-Linux kernels.
Indeed, this would help a lot in some corner cases. > For example for iotop I went with an arch:linux-any package instead of > arch:all, the package is fairly small so the duplication isn't a big > issue. > Personally I think you should hardcode the ACPI architectures and > accept the minor duplication. Well, that's what I thought to do at the beginning, but the docs say that binary package duplication is a bad thing, and I didn't know if four copies of a 13 KB package (so a waste of 49 KB per mirror, which would seem negligible unless you're a purist) was an "acceptable" exception, hence my asking here for advice. Now I have two opposite opinions, which is quite disturbing :) I finished implementing Ondřej Surý's solution but I didn't push the changes to Git yet, let alone upload the package, so it's still time to change my mind. In the end, it all comes down to tiny storage space waste vs a no-op DKMS package. Anyone wants to chime in to tip the scales in favor of one solution over the other ? Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
