Hi Sven and all others, Am 2003-04-11 14:50 +0200 schrieb Sven Luther: > You just need to add a lintian override, you know how to do this ? No, I dit not, but thanks to your explanation, I do now. I installed the override, and it works fine. > > My current approach is to build a bytecode package (arch: all) for > > the "general case" (this would binary-depend on ocaml-base) and a > > package offering native versions for all platforms supporting it. > you need to call the bytecode version planet-byte, and have it > provide planet, and call the native code version planet. The > apt/dpkg magic will prefer a true package before an virtual one, so > if you install plant, you will get the native code version if it > exists and the bytecode version if it does not. installing > planet-byte will get you the bytecode version, no matter what. > Naturally, you have to have the two packages to conflict so they > don't install at the same time. I admit that I would have never conceived that on my own. But it works very well and I understand the principle now. Thanks for the detailled explanation. > Now, this suppose that you remove all the -custom flags that upstream > has used in the Makefiles, I already did, since otherwise I do not get real bytecode. -custom creates an ELF executable, without -custom real bytecode files with a shebang line is created. > and is not possible or good if you have C bindings included, like > the advi package does for example. The correct way is to either say > you don't care and package a -custom bytecode or a native code, both > arch: any, or to separate the binding library in its own package, > which will be arch: any and provide both the bytecode and nativecode > libraries, and build the app depending on this library. I do not fully understand that but I will investigate what C-Bindings in ocaml programs are. > I would say the second only makes sense if the library can be used by > other people too, or if the app is really big that not having 5 extra > copies in the archive is a good thing. The application is pretty small (bytecode package: 324 kB). But if I understood you and the -custom flag correctly, -custom will create arch-specific pseudobytecode packages, whereas without -custom true arch-independent files are created (see above). Did I get this right? I will upload an updated version of my package in a few minutes. BTW: I use ocaml from unstable now. :-) Thanks a lot! Martin -- Martin Pitt home: www.piware.de eMail: martin@piware.de Verteidigen Sie Ihre Freiheit und Ihre Rechte! Stoppt TCPA! Defend your freedom and your rights! Stop TCPA! http://www.notcpa.org
Attachment:
pgpqjHKFjoTjO.pgp
Description: PGP signature