Hi, le mer 16-01-2002 � 18:16, Sven a �crit : > Hello, ... > > I have just finished building ocaml 3.04-5, which splits away ocamlc.opt, > ocamlopt.opt and ocamllex.opt into a package called ocaml-native-compilers > (not a great name, i think). > > Does someone have any kind of objection or remark to this ? Or maybe a better > name ? >
I have an objection: if I understand well what you did, this mean that ocamlopt.opt for instance will not be provided with the "ocaml" package. The package I maintain has a "Build-Depends: ocaml". Its configure script checks whether ocamlopt.opt is available and if so, use it instead of ocamlopt (if ocamlopt is not available, it uses ocamlc). If ocamlopt.opt is no longer included in ocaml, this means that it will never be build with ocamlopt.opt (at least with buildd) as I cannot put a dependency on ocaml-native-compilers if I want the control file of my package to be architecture-independent (I like the portability of ocaml, I would not like to deal with architecture-dependent problems). Is not this a pity? Maybe a fix would be to provide a "fake" ocaml-native-compilers for architecture that do not support ocaml-native-compilers? Judica�l. -- [EMAIL PROTECTED], http://www.lri.fr/~jcourant/ (+33) (0)1 69 15 64 85 "Heureux ceux qui savent rire d'eux-m�mes : ils n'ont pas fini de s'amuser !" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
