d/control: Add comments about why some packages are Arch: any
At first glance these packages seem like they should be
Architecture: all, but in fact they cannot.
Simon McVittie
3 years ago
94 | 94 | need for a central server. It is primarily intended to be used in |
95 | 95 | ad-hoc networks which lack a DHCP server. |
96 | 96 | |
97 | # Note that this cannot be Architecture: all - even though it is pure | |
98 | # Python! - because it contains an architecture-specific path to | |
99 | # service-types.db, which has a format that varies with word size and | |
100 | # endianness. | |
97 | 101 | Package: python3-avahi |
98 | 102 | Section: python |
99 | 103 | Architecture: any |
169 | 173 | This package contains the Avahi common library, which is a set of common |
170 | 174 | functions used by many of Avahis components and client applications. |
171 | 175 | |
176 | # Note that this is Architecture: any, not Architecture: all, due to the | |
177 | # architecture-dependent service-types.db file. | |
172 | 178 | Package: libavahi-common-data |
173 | 179 | Section: libs |
174 | 180 | Architecture: any |