Bug#1144627: debian-policy: Introduce architecture as 2.6 and document baseline
Bastien Roucaries <[email protected]>
| Newsgroups | gmane.linux.debian.devel.policy |
|---|---|
| Message-ID | <12953976.O9o76ZdvQC__5555.30813742138$1786970847$gmane$org@debian-ei> |
Le lundi 17 août 2026, 13:48:16 heure d’été d’Europe centrale Holger Levsen a écrit : > On Mon, Aug 17, 2026 at 12:16:37PM +0200, Bastien Roucaries wrote: > > [improvment] > > - Next step will be to document generally multi arch and partial arch. > > https://www.debian.org/doc/debian-policy/ch-controlfields.html#multi-arch > has finally been documented... > > (though I dont blame you for missing this, it was undocumented for >10 years.) Yes I know but section 2.6 will be more a philosophical introduction to multi-arch something along Multi‑Arch in Debian is the mechanism that allows a single system to install and use packages from multiple architectures at the same time. It extends the architecture context so that libraries, headers, and binaries from foreign architectures (like i386 on an amd64 machine) can coexist cleanly without file conflict. Individual packages declare their support for this feature, and influences the way dependencies are handled. Moreinformation could be found in section 5.6.34 thanks holger for documenting. > > >
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmqDAoIACgkQADoaLapB CF+6/hAAnFDfMJQwGlU/t8Y5uDOWpqcfN/SqQJeWV5qOoBnDgX2FrbF0EI9n1Y/r 3PSRKSZ3GlvlIL9IOctUrWf0kP/KtqSOFtFl7roG2pzH+NKlD7TMqWoSE/nosdXv bga4+/wai5FTbIm0B6P/hOklJSATdfV79GzItPv6iTBLCG2BaCCpKMBKOoM0UJiO BeiaXzgVBzzr9H1Jzi7/df3OzLGhVdfPzOc78s8XfYVmAqw9JD/qpKXegcQ3j0/9 xMOrwzimqeFsEI0W8C1+mjilCt54X7jnsbSbFfB+NJuxTfP/I62Dw8qf6eK1FkTg H13DYM5rDNMP3mhDuRzST/qFK/g06N9FJPiNMVt/gWfpi6f/nwM6xlAYEcbzd3P9 fROw/aPZLaYPIKGC76vtpubqGuQsp/26GyLzYm/3N8tJieo5BW2NpCJwLtZmDudX z+PMtenK1zOd1eBss8Mm/ekGYXDmLGo4qbjqtZtDqDgCqU7apqrNyrzsgcCxrMKa L0QINwnezffqG1+yWj3ckU8PnPwbPeK2JHP8q3cawCPyb9t3YvxGHrE2iRnhlvbb w4+stDzljl4ZwhMydNnZEfZ6rWqYGwuh4br2jVt49r2Mmn3uKGb8KAjVZ89nnAAn MiLjV/volQ42mss5Sctk6h5dH8WmU5px+2YMtMFegj9m3CJQCpU= =Cs4O -----END PGP SIGNATURE-----