Martin Michlmayr wrote:
> FWIW, I agree with Adrian's interpretation [*]. "the packages in
> main" "must not require a package outside of main" for "execution"
> (... "Recommends"). While this sentence is fulfilled on i386, it is
> violated on !i386 which imho is a Policy violation.
What would you say about the case of a source package that produces some
Arch: any packages and some Arch: all packages, but which is only
compiled for certain architectures? For instance, cernlib isn't
supported on 64-bit, so I've had it added to Packages-arch-specific. It
has some Arch: all packages that depend or recommend Arch: any packages,
==> said Arch: all packages are uninstallable (or have an unsatisfiable
Recommends) on {alpha,amd64,ia64}. Is this considered to be against policy?
If so, I am not quite sure what to do about it, since making some of the
data packages Arch: any would tremendously bloat the archive. I guess
they could just Suggest the relevant libraries, but this sort of twists
the meaning of Recommends vs. Suggests -- no one would want to have a
data package installed without the corresponding library package.
regards,
--
Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department
WWW: http://www.princeton.edu/~kmccarty/ Princeton University
GPG public key ID: 4F83C751 Princeton, NJ 08544
