On Fri, Feb 07, 2003 at 06:05:24PM +0100, Sven Luther wrote: > On Fri, Feb 07, 2003 at 05:22:16PM +0100, Sven Luther wrote: > > Hello everyone ... > > > > At apt-source : > > > > deb http://people.debian.org/~luther/ocaml ./ > > > > You can find the new ocaml packages version 3.06-16. After a bit of > > testing from me and you (and upgrade testing) i will upload those to > > debian/unstable. Once they are fully built on all arches (not before the > > gcc-3.2/libc6 sparc bug is solved though), i will upload a ocaml (and > > ocaml-base, ...) package which is empty but depends on the ocaml-3.06-1 > > versions. This should solve the build dependencies we were > > experimenting, and allow us to continue enjoying the rather clean > > ocaml-3.06-1 dependencies we are using right now. > > > > It will also further facilitate the migration between one upstream > > version of ocaml and the next, and is the same thing other are doing > > (gcc for example). > > > > A current problem i have is with upgrading, i did not do any trick for > > upgrading from ocaml to ocaml-3.06-1, but since the former provide the > > later, it may cause problem. Maybe i should add a conflict: ocaml (< > > 3.06-16) and also a replace: ocaml. > > I have added the conflict and the replace, it upgrades smoothly, so > please, add the above line to your apt-sources, and upgrade to it. It > should go smoothly for everyone. Please provide feedback (on sucess and > on failure) so i can upload it to unstable nextly.
Well, apparently nobody cares, i uploaded the package yesterday, but it need first to be reviewed by the ftp-masters. Anyway, i was thinking that this should be able to go into testing without the bazillion of libraries, since uploading ocaml-3.06 into testing will not stop the ocaml 3.04 that is currently in testing to work, and all the libraries and other packages which depend on it would be fine. Sure, they could not be installed separatedly, but there should be no problem in having ocaml-3.06 packages and ocaml 3.04 in testing at the same time. Then the libraries and other packages will go into testing in little group corresponding to connected components in the dependency graph or something, as these packages will replace their 3.04 versions. This could be avoided if we do the same trick to libraries i just did to ocaml, and would correspond to what is done with C shared libraries, which would also have other benefits i will be going into below. Another issue i just thought about, while responding to a mail on the caml-list, is that we should also change the ocamlrun binary so that it is named ocamlrun-version, so that multiple version of ocaml-base (with their libraries) can be installed at the same time, so it is possible to transparently run bytecode executables built with older versions of the ocaml packages. One way to achieve this, is that once the migration is completed, i would upload a runtime only package of the previous version, and the same goes for libraries. This would mean somehow integrating the ocaml version in the library names, libfoo-ocaml-3.06 and libfoo-ocaml-3.06-dev for example, and when a new ocaml version enters the archive, still maintain a version of the libraries runtime (the dllfoo.so) that was built with the previous version of ocaml. This is an orthogonal issue than the library dependency evoked by Stefano though. Friendly, Sven Luther
