Re: Multiarch file overlap summary and proposal
Ian Jackson <email@example.com> writes:
> Russ Allbery writes ("Multiarch file overlap summary and proposal (was: Summary: dpkg shared / reference counted files and version match)"):
>> 5. Data files that vary by architecture. This includes big-endian
>> vs. little-endian issues. These are simply incompatible with
>> multiarch as currently designed, and incompatible with the obvious
>> variations that I can think of, and will have to either be moved
>> into arch-qualified directories (with corresponding patches to the
>> paths from which the libraries load the data) or these packages
>> can't be made multiarch.
> Yes. Of these, arch-qualifying the path seem to be to be obviously
> the right answer. Of course eg if the data files just come in big-
> and little-endian, you can qualify the path with only the endianness
> and use refcounting to allow the equal-endianness packages to share.
Preferably -data-be:all and -data-le:all packages if they can be build
irespective of the buildds endianness.