Out of curiosity, what was tedious to maintain there? One thing that's come up in both Mirage and XAPI is to have a script that 'splices' a released package from one remote to another. That would let us upload stable cuts to a working remote, and then move them over to opam-repository. Would that sort of thing help Ocsigen as well?
-anil > On 19 Feb 2015, at 01:01, Drup <[email protected]> wrote: > > The opam ocsigen repository has not been updated since quite some time now, > and for various reasons, it's very tedious to maintain. Thus, we decided to > remove it. > > For people using it, I really advise you to use the released versions of each > packet if possible. > If you absolutely want bleeding edges (for example, if you use eba), just use > opam pin. > > For each ocsigen package, you should be able to use the following command > line and it will directly be pinned to the dev version: > > opam pin add the_packet --dev-repo > > > Special note for people using eliom-base-app, you need a special branch of > eliom, which you can pin with: > opam pin add eliom https://github.com/ocsigen/eliom.git#sharedreact > > I will remove the repository by the end of the week. > _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
