From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id CD0417F720 for ; Sat, 12 Apr 2014 01:39:01 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=pra; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=mailfrom; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp.webfaction.com) identity=helo; client-ip=74.55.86.74; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="postmaster@smtp.webfaction.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmsCAHl8SFNKN1ZKlGdsb2JhbABZg0GCRoEhwBeBMw4BAQEBBwsLCRIqgiUBAQEDASNWBQsLDgwCJgICRwIBDQYbh2wIBAmocKJYEwSBKYtGgUozB4JvNYEUBJ8cF48i X-IPAS-Result: AmsCAHl8SFNKN1ZKlGdsb2JhbABZg0GCRoEhwBeBMw4BAQEBBwsLCRIqgiUBAQEDASNWBQsLDgwCJgICRwIBDQYbh2wIBAmocKJYEwSBKYtGgUozB4JvNYEUBJ8cF48i X-IronPort-AV: E=Sophos;i="4.97,845,1389740400"; d="scan'208";a="56744162" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail3-smtp-sop.national.inria.fr with ESMTP; 12 Apr 2014 01:39:00 +0200 Received: from [172.20.10.2] (35-229.197-178.cust.bluewin.ch [178.197.229.35]) by smtp.webfaction.com (Postfix) with ESMTP id 78899226F34D; Fri, 11 Apr 2014 23:38:40 +0000 (UTC) Date: Sat, 12 Apr 2014 01:38:36 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: David Allsopp Cc: "=?utf-8?Q?caml-list=40inria.fr?=" Message-ID: <660235A830144A6DB09C9B6A0538E5EF@erratique.ch> In-Reply-To: References: <77DB6A35979C449C90DEAC36896DA971@erratique.ch> <53c5ec5fa458ca0ae78f13ff79d9abf5@in.tum.de> <9636C678CAA541CCB505CE8771722A68@erratique.ch> <063FC564F6B44EA5AB1CF1D5589996D0@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0) Le samedi, 12 avril 2014 =C3=A0 00:33, David Allsopp a =C3=A9crit : > Windows can't do anything with that. However, most people compiling OCaml= packages on Windows expect to use bash (either from Cygwin or MSYS), where= the scripts would run as on Unix. Are you sure that Windows compatibility = is already a problem? No, I just thought that you wouldn't get a shell on windows. So maybe you a= re right, nothing needs to be done, reports welcome. That being said with an ocaml rewrite I'd abstract the thing a little bit m= ore to make it more DRY (I deliberately prevented myself of doing that in s= h: possible but guaranteed to become un-rereadable once you figured out the= magic invocations) =20=20 > s long as you don't do anything exotic with command line parameters (quot= ing can be very weird for the Windows command processor, cmd, which is what= Sys.command uses) then yes, Sys.command will be fine, and the same as on U= nix. Ok and ocamlbuild is ocamlbuild not ocamlbuild.exe ? > In passing, it does have to be said that getting Windows support automati= cally from your build system is something that OASIS does... At an unacceptable time cost, level of complexity and insulation from your = build system=E2=80=A6 oasis maybe fine if you distribute a single package a= nd have time to loose fighting with the system. It's not when you formally = release a dozen of packages (and plan to release more).=20=20 At the risk of repeating myself I need simple, reliable, efficient release = and packaging workflows: right now if I need to perform a 5 min administrat= ive task on each of my released packages that's already an hour of my time = that is gone and I hate admin tasks. So it turns out that in *my* case, I'm= very well served by opam .install files, ocamlbuild and a 100 loc, trivial= , shell script [1] that I hope I'll be able to kill if we once get a good b= uild system that has decent packaging support and handles .install file gen= eration for me. Best, Daniel [1] https://github.com/dbuenzli/pkgopkg/blob/master/pkg/pkg-builder