[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Arch-dependent Depends


I maintain a set of packages which depend openmpi which is missing on
certain architectures.  To get around the latter problem, I use
arch-dependent Build-Depends to specify openmpi where available and lam
otherwise (though the buildd report for hypre on s390 shows it doesn't
seem to understand this directive).

Because hypre upstream doesn't make static libs, and I got tired of
making a new patch with every release, libhypre-dev is arch all without
static libs.  However, it needs to depend on openmpi on some arches, and
lam4-dev on others.  Using the same syntax as Build-Depends doesn't

Is there a way to do this, or do I need to make libhypre-dev arch any
and set the dep using substvars, even though its contents are
arch-independent?  I notice that Policy section 7.1 provides for
arch-dependent Build-Deps, but there's nothing similar for Depends...

[Please CC me in replies.]

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: