[opam-devel] bundling

[Louis Gesbert]

That's awesome, thanks ! I am in the process of reviewing the patch ; in its current state it will work for basic packages but won't handle patches, .install files and such more advanced features. I am wondering also if this should fit in opam itself, or in an external tool like opam admin / opamfu, as this is mostly independent from the current opam installation (except for repositories used). Making it external would ensure there is no issue with the current state being loaded and used for filtering the commands.

>  * bundling of ocaml itself

When my compilers-as-packages branch lands, hopefully this won't require any more work for bundling :)

>  * better error messages (e.g. when depext is missing), though that can be checked by configure script

Integrating proper depexts and/or post-messages processing in a generated shell-script sounds very tedious, not sure what the best approach would be here but just outputing the info at bundle-generation time to help document may be good enough for a start.


These are just details though, this is really cool and will just need a bit of polishing to make sure it integrates nicely without unexpected errors.

Louis


Le lundi 24 février 2014, 18:13:37 ygrek a écrit :
> Hello,
> 
>  https://github.com/ocaml/opam/pull/1190
> 
>  This is not 100% complete, but it helps me to solve my current issue, namely a single click install of ocaml software.
>  My further goal is to use this to unbundle mldonkey so that it can be built with ocamlfind dependencies
>  by the developer and still distributed as a single archive for the end-users.
>  TODO:
>  * bundling of ocaml itself
>  * better error messages (e.g. when depext is missing), though that can be checked by configure script
>  * windows?
> 
>  I wonder what you think about it.
> 
>