Re: splitting up the ocaml package: summary

[Christian Perrier <bubulle@debian.org>]

> Humm... the split is fine with me, but i just don't like name :
> pkg                    depends               contents
> -------------------------------------------------------------
> ocaml                  everything            everything
> ocaml-base             ocaml-interpreter
> ocaml-interpreter      
> ocaml-compilers                              (pseudo package)
> ocaml-native-compilers                       compilers *.opt 
> ocaml-byte-compilers                         compilers *.byte
> liblabltk-ocaml                              labltk stublibs
> liblabltk-ocaml-dev     liblabltk-ocaml      labltk header
> libbase-extra-ocaml                          extra stublibs 
> libbase-extra-ocaml-dev libbase-extra-ocaml  extra header
> libgraphics-ocaml                            graphics stublibs
> libgraphics-ocaml-dev                        graphics header

I have had a look to my geneweb package.

Currently, its dependencccies are:

Build-Depends: .../... ocaml-best-compilers, ocaml (>= 3.04), .../...

I'm not sure to remember why both are required, by the way....anyway,
this currently works by making it use the native compiler on platforms
which have one and the byte compiler otherwise....

My understanding of the above scheme is that I should now use only
"ocaml-compilers" which is a pseudo-package for "native" or "byte"
depending oin the platform.

Am I right?

I suppose of course that I need waiting for these to be uploaded in
unstable and built on all arches for uploading a modified
geneweb. Maybe waiting for the transition packages to reach testing is
even better as I will be sure that geneweb entering testing will not
be stucked by some weird thing preventing the ocal packages to enter
testing.