From: Alain Frisch <alain@frisch.fr>
To: Caml mailing list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Shared run-time DLLs for commerce
Date: Mon, 07 Jan 2008 16:54:45 +0100 [thread overview]
Message-ID: <47824B45.1000507@frisch.fr> (raw)
In-Reply-To: <200801071503.26977.jon@ffconsultancy.com>
Jon Harrop wrote:
> We're currently distributing .cma files but the main problem is that they're
> far too brittle
Ok, your concerns are not really about being able to distribute shared
libraries, but rather being able to distribute binary libraries that
don't depend on precise version of other dependent libraries and of
OCaml. I don't think you'll get them any time soon.
Suggestions:
1. Distribute the source code, even without an open source license. I
cannot imagine this would reduce your sales, but you know better.
2. Distribute a fully packaged OCaml distribution that includes all the
dependent libraries (your users will be free to add third party libs as
well).
3. Obfuscate the parts of the source code you want to keep secret.
Camlp4 might help here.
4. Distribute a static binary that plays the role of a server that
encapsulates all your precious trade secrets + a client library
distributed in source code.
> Ah, I hadn't noticed these .cmxs files. They look good but I assume they are
> also brittle?
Yes, indeed.
-- Alain
next prev parent reply other threads:[~2008-01-07 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:30 Jon Harrop
2008-01-07 13:03 ` [Caml-list] " Alain Frisch
[not found] ` <200801071503.26977.jon@ffconsultancy.com>
2008-01-07 15:54 ` Alain Frisch [this message]
2008-01-07 17:32 ` Kuba Ober
2008-01-07 19:51 ` Jon Harrop
2008-01-07 21:17 ` Stefano Zacchiroli
2008-01-08 19:39 ` Christophe TROESTLER
2008-01-08 19:42 ` Jon Harrop
2008-01-08 20:18 ` Richard Jones
2008-01-08 16:03 ` Richard Jones
2008-01-08 18:35 ` Jon Harrop
2008-01-09 9:17 ` Alain Frisch
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=47824B45.1000507@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@yquem.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