On Mon, Sep 30, 2002 at 03:28:29PM +0200, J?r?me Marant wrote: > On Mon, Sep 30, 2002 at 03:32:47PM +0200, Sven Luther wrote: > > > This leaves more flexibility to the user, and would allow to do a > > binary:all package build even on a native code supporting arch. > > Which is only true for libraries. It isn't for binaries since > standalone byteocde programs embed the bytecode interpreter > which is architecture dependent.
??? I don't understand you. The idea is to build one package arch: all which you build with the bytecode compiler (and without the -custom flag). The resulting executables will be /usr/bin/ocamlrun script, as can be seen with the ledit package for example : $ file /usr/bin/ledit /usr/bin/ledit: a /usr/bin/ocamlrun script text executable And then upload a second package which conflicts and replace, and whatver, which contains the native code version. Friendly, Sven Luther
