caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: David MENTRE <dmentre@linux-france.org>,
	"opam-devel@lists.ocaml.org" <opam-devel@lists.ocaml.org>
Cc: Roberto Di Cosmo <roberto@dicosmo.org>,
	Dagnat Fabien <fabien.dagnat@telecom-bretagne.eu>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Opam use for teaching lab infrastructure
Date: Fri, 20 Sep 2013 10:50:18 +0100	[thread overview]
Message-ID: <0BB2D8EF-DFED-4970-9D3E-3A43ED1BFCF2@recoil.org> (raw)
In-Reply-To: <CAC3Lx=bOr9r+-Puk5XOrpKsyB5Rnjygxf1+cBQ+_MG64xZokPw@mail.gmail.com>

On 20 Sep 2013, at 10:40, David MENTRE <dmentre@linux-france.org> wrote:
> 
> 
> 2013/9/19 Roberto Di Cosmo <roberto@dicosmo.org>:
>> 
>>      You may need to help them installing the necessary development environment
>>      (gcc, m4, devl libraries, etc.), I do not know how to avoid this on a
>>      random laptop :-(
> 
> I am trying this approach: installing opam on a fresh Debian virtual
> machine for "students". With opam, how do you guess the needed
> external libraries?
> 
> With tarballs, I am usually reading the INSTALL or README file and
> install needed Debian packages. But how do I access to this
> information for opam packages? Is there a list somewhere of external
> (to opam) dependencies?

I maintained a rough set of monolithic dependencies in the jenkins/ source
directory of OPAM:
https://github.com/OCamlPro/opam/blob/master/jenkins/10-opam-prepare.sh

This is temporary, as OPAM 1.1dev has better support for describing external
dependencies within the package description via the `depexts` field.
The design of this is sketched out in:

http://anil.recoil.org/2013/09/09/ocamlot-autotriaging.html
(look for 'external system dependencies')

I'm still gluing together a sample version of this on Debian/OpenBSD, so
I'll mail this list requesting maintainers to help describe their external
dependencies when I have a working local setup with some sample packages.

For now, contributing to the monolithic install script above is welcome,
as I can use that as a reference when porting dexpexts over.

cheers,
Anil

  reply	other threads:[~2013-09-20  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19  9:38 Dagnat Fabien
2013-09-19  9:52 ` Francois Berenger
2013-09-19 10:50 ` Roberto Di Cosmo
2013-09-20  9:40   ` David MENTRE
2013-09-20  9:50     ` Anil Madhavapeddy [this message]
2013-09-20 12:12       ` David MENTRE

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=0BB2D8EF-DFED-4970-9D3E-3A43ED1BFCF2@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=fabien.dagnat@telecom-bretagne.eu \
    --cc=opam-devel@lists.ocaml.org \
    --cc=roberto@dicosmo.org \
    /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).