"Roberto C. Sanchez" <firstname.lastname@example.org> writes:
> On Sun, Jun 12, 2005 at 03:21:54PM +0200, Adeodato Simó wrote:
>> [People from debian-ocaml-mail, please keep -mentors CC'ed.]
>> * John Skaller [Sun, 12 Jun 2005 16:27:21 +1000]:
>> > I could use a 'build-recommends' dependency,
>> > but I understand 'recommends'
>> > is only available for the binary package, not the source.
>> > Is this correct?
>> > The situation: the packaging machine requires 'ocaml'
>> > to make binaries from my source package, but if
>> > 'ocaml-native-compilers' is also installed it will
>> > do so faster, however that package is not available
>> > on all architectures.
>> > This isn't an essential feature, but here is a case,
>> > possibly isolated, where it could be useful.
>> Normally, one resolves this and similar situations like this:
>> Build-Depends: ocaml-native-compilers [!m68k !mips !mipsel !s390],
>> ocaml [m68k mips mipsel s390]
> Couldn't you also Build-Depend on 'ocaml-native-compilers | ocaml'?
> That would look first for ocaml-native-compilers and then if that is not
> available, for ocaml. Plus, if the ocaml-native-compilers package
> becomes available for other architectures, it does not require a
> modification to the Build-Depends to take advantage of it.
No it wouldn't.