…c links are sometimes encountered in the folding tree
… over HTTP doesn't work ... Cannot upload anything with that, and need an urls.txt file describing the site contents
* We keep a list of alias => compiler version up-to-date. * opam switch -list gives a precise descriptions of installed aliases and avaible compilers * opam init -alias foo initialise opam with the right alias for the compile * opam init -comp 3.12.1 -alias foo install the version 3.12.1 of the compiler, and it will works even if no OCaml compiler exist in the current path
So now, compiler description files can be downloaded from OPAM repositories. There is no way to upload compiler descriptions yet (and I don't think it will in a near future).
…processes. Now a command is a list of words, which is much safer (and we are not allowed anymore to use pipes).
…ted depending on the current OCaml version set.
The file is $opam/opam.lock and it contains the process id which has taken the lock.
…pluggin. * all tests pass * To use this kind of repo: 'opam init --kind server <name> <address>' or 'opam remote -add --kind server <name> <address>' * the default is still the read-only 'rsync' kind
It compiles, but untested. The basic idea is to have a git repository storing OPAM, description files and git urls of dev packages: * opam-git-init clones the repository at the right place * opam-git-download clones the git repository for the right pacakge, and call git-archive to create a .tar.gz which is copied at the right place (to follow the OPAM repository pluggin protocol) * opam-git-update updates the main repository to look for new packages and then updates each already cloned packages to see if they need to be updated