caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrew Herron <thespyder@programmer.net>
To: Jordan W <jordojw@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] CommonML: An opinionated build/package/develop workflow on top of CommonJS
Date: Wed, 25 Feb 2015 13:12:20 +1000	[thread overview]
Message-ID: <CALATSMb6dDmCbMemo=7BCUnTjg8VdVLknBmqOyLmhQ6kyz2GDQ@mail.gmail.com> (raw)
In-Reply-To: <CAPOA5_5KZXXPaJ7OktWVqzN86Ex4joDrdXrQQHvW_hUwRe0cJg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

I've been thinking about this a bit, as a JS developer who is experimenting
with OCaml (in my non-existant free time). I don't use the CommonJS flow in
my day job although we do have many projects which our internal
build/dependency system combines with similar results.


On Wed, Feb 25, 2015 at 6:26 AM, Jordan W <jordojw@gmail.com> wrote:

>
> I created a proof of concept called CommonML, which lets developers use
> their familiar CommonJS workflow with OCaml:
> https://github.com/jordwalke/CommonML


My initial thoughts were to stick with the OPAM repositories; even if I
have to make a local OPAM repo server it seems like leveraging the existing
ecosystem is a good idea. My experiments use a dedicated `opam switch` for
the project, enforced by the Makefile (which might not scale to multiple
projects, but I haven't tried that yet).

I can think of one good reason to share OCaml and JS dependencies on the
same server though, and that's including a JS library in a js_of_ocaml
project. Certainly using a single package.json file to specify both JS and
OCaml dependencies is an interesting idea (even if under the hood we
eventually find a way to use OPAM for the OCaml projects).

Cheers,
Andy

[-- Attachment #2: Type: text/html, Size: 1703 bytes --]

  reply	other threads:[~2015-02-25  3:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 20:26 Jordan W
2015-02-25  3:12 ` Andrew Herron [this message]
2015-02-25  5:58   ` Jordan W
2015-02-25  6:24     ` Andrew Herron

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='CALATSMb6dDmCbMemo=7BCUnTjg8VdVLknBmqOyLmhQ6kyz2GDQ@mail.gmail.com' \
    --to=thespyder@programmer.net \
    --cc=caml-list@inria.fr \
    --cc=jordojw@gmail.com \
    /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).