From: Francois BERENGER <berenger@bioreg.kyushu-u.ac.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Create a deployable application unit from OPAM?
Date: Tue, 3 Apr 2018 09:25:30 +0900 [thread overview]
Message-ID: <3e181a7c-70e3-cf5f-5b0f-6c095e77ef69@bioreg.kyushu-u.ac.jp> (raw)
In-Reply-To: <4945274.q1Lr0Fu7B2@agaric>
On 03/30/2018 11:11 PM, Louis Gesbert wrote:
> There is no perfect solution at the moment, as there are still some hiccups with relocation of quite a few opam packages, but there are a few options:
>
> 1. Not precisely what you were asking for, since it involves re-compiling, but opam-bundle¹ can generate an all-in-one package that can easily be deployed to a different system and will bootstrap OCaml, opam, the packages and their dependencies, and can put wrappers for the binaries to your PATH. This takes a while, but avoids any relocation problems and is quite reliable.
> The bundle could also be used as base for a container, or even copied across similar hosts (to the same location), and just the wrappers reinstalled.
Is opam-bundle production ready?
For example, is it mature enough so that the coccinelle people can use
it to ship a source-based version of coccinelle to their users, without
requiring users to install opam first?
Regards,
F.
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2018-04-03 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 16:31 Hans Ole Rafaelsen
2018-03-29 18:13 ` David Scott
2018-03-29 18:50 ` Hans Ole Rafaelsen
2018-03-29 22:44 ` Gerd Stolpmann
2018-03-30 14:11 ` Louis Gesbert
2018-04-02 18:17 ` Hans Ole Rafaelsen
2018-04-03 0:25 ` Francois BERENGER [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e181a7c-70e3-cf5f-5b0f-6c095e77ef69@bioreg.kyushu-u.ac.jp \
--to=berenger@bioreg.kyushu-u.ac.jp \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).