peter green wrote:
[...]
> This leads to the building of
> uninstallable packages which in turn leads to problems with testing
> transition of packages.
>
> Currently there are two workarounds for this situation
>
> 1: manually alter the package's architecture list to limit building to those
> architectures where runtime dependencis
> 2: add an artificial build-dependency
For completeness, it's probably worth mentioning a third option:
3: use the architecture list to document fundamental portability hurdles
and packages-arch-specific[*] to document accidental ones
[*]
http://www.debian.org/doc/manuals/developers-reference/pkgs.html.en#packages-arch-specific
--
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/20111129200854.ga9...@elie.hsd1.il.comcast.net
