caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Alexy Khrabrov <deliverable@gmail.com>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: ocamlfind ocamlopt.opt?
Date: Wed, 18 Mar 2009 16:35:36 +0000	[thread overview]
Message-ID: <84346841-6793-45A0-8C99-1D96C79AC062@recoil.org> (raw)
In-Reply-To: <6F35AFCC-9A69-44C9-BA57-58A43913856F@gmail.com>

On 18 Mar 2009, at 16:19, Alexy Khrabrov wrote:

>
> On Mar 18, 2009, at 8:21 AM, Anil Madhavapeddy wrote:
>> I rather like MacPorts since it's easy to add a local override with  
>> upgrades and so on (e.g. backporting the fix for fork+threads on  
>> MacOS X).  I've got my OCaml macports repo up at:
>>
>> http://github.com/avsm/darwinports/
>>
>> with a bunch of fixes and upgrades.  I'll be feeding these upstream  
>> when I get a chance but you can use this repo to grab my latest bits.
>
> Anil -- this is awesome!  This is exactly why source-based beats  
> packaged -- it takes just a git push origin master to have a new  
> port.  So what do you do for the rest -- just get them from tarballs  
> and install with findlib?  I think the set should be self-contained  
> in dependencies...

I just knock up a new Portfile when I need anything these days; it  
only takes a few minutes and means you never forget which of the  
myriad OCaml libraries are dependencies when you try to get the  
project up and running on another system.

-anil


      reply	other threads:[~2009-03-18 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 18:37 Alexy Khrabrov
2009-03-17 22:13 ` Sylvain Le Gall
2009-03-17 22:53   ` [Caml-list] " Alexy Khrabrov
2009-03-18 12:21     ` Anil Madhavapeddy
2009-03-18 16:19       ` Alexy Khrabrov
2009-03-18 16:35         ` Anil Madhavapeddy [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=84346841-6793-45A0-8C99-1D96C79AC062@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=deliverable@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).