Re: Cherry-picking modules (was Re: [Caml-list] [ANN] OCaml Reins 0.1 - Persistent Data Structure Library)

[Mike Furr <furr@cs.umd.edu>]

skaller wrote:

> This is true .. but you're missing something, which is slightly
> surprising considering you're the maintainer and DD manager
> of the Debian package for Felix ..

I believe the main point here is that you are bending what I consider
best practice for felix because it is still in development and you want
to speed its adoption.  I do understand that.

> None of my clients will be needing this library to use it,
> because they're not (using Felix as) Ocaml programmers.
> 
> If I used it, it would be used ONCE by users to build the 
> Felix executable and discarded. Already, Python, Ocaml 
> and C++ are needed for this single build.

You should no more expect them to build the reins library then for the
gcc authors should expect you to build all of the dependencies of
gcc/g++ (of which there appear to be >40 in the debian/control file for
that package).  When you distribute the felix binary, all of its ocaml
libraries are statically linked in, so they don't have to download
anything outside of your binary (which is the downside of your choice to
do source releases).

> will your build scripts work on Windows?
> Will Omakes and findlibs and Ounits build scripts build
> transparently on Windows?
I haven't tested it, but I would be very surprised if they didn't.

> My build script do -- they're platform independent.
> 
> [Yes, I know Omake is designed specifically to work on Windows
> to enable platform independent builds]

And I am relying on that fact.  Good thing I didn't just cut and paste
the relevant omake code to compile my stuff on linux. :-p

-mike