On Wed, Jun 26, 2002 at 11:12:52PM +0200, Jérôme Marant wrote: > >> Ocamlsdl needs ocamlopt and it seems that ocamlopt is not > >> provided by all architectures (not suprisingly). > >> > >> So what is the best way to handle this? Should I specify > >> all the architecture providing ocamlopt in the Architecture: > >> field? > > > > Aren't these exactly the same architectures than those that have the > > ocaml-native-compilers package? In this case a build-depends on > > ocaml-native-compilers might do the trick, though it is not exactly > > in the sense of policy. > > Well, I don't need native compilers to build the package, so > build-depending on such a package may not help at all.
I just thought that, for every architecture a, there is ocamlopt for target architecture a if and only if there is ocamlopt.opt running on architecture a. > Furthermore, I don't know how autobuilders behave when some > dependencies are unmet: is the package not considered for > the given architecture or is it considered as a failure? Yes, that would be a failure. Would that be a problem? AFAIK, it wouldn't prevent passage to testing when binaries for the architecture in question never existed. > BTW, native compilers run on: > > ocaml-native-compilers | 3.04-13 | unstable | alpha, arm, i386, > powerpc > > I've seen many more supported architectures in ocaml CVS (ia64, > parisc), > where have they gone ? Maybe Sven knows? I'm not sure whether all the autobuilders are active. ia64 is, hppa might be not? -Ralf. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
