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 C5D0F7FACD for ; Sat, 20 Sep 2014 16:59:46 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jun.furuse@gmail.com) identity=pra; client-ip=74.125.82.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jun.furuse@gmail.com"; x-sender="jun.furuse@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of jun.furuse@gmail.com designates 74.125.82.43 as permitted sender) identity=mailfrom; client-ip=74.125.82.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jun.furuse@gmail.com"; x-sender="jun.furuse@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f43.google.com) identity=helo; client-ip=74.125.82.43; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jun.furuse@gmail.com"; x-sender="postmaster@mail-wg0-f43.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkACAHiVHVRKfVIrm2dsb2JhbABgg2FXBLhWj1iBa4dNAXQIFgERAQEBAQEGCwsJFCqEAwEBAQMBEi4BGxICCQEDAQsGBQsNDSEiAREBBQEKEgYTEhCIBwEDCQgNoQJtjSKDEIh0ChknAwpmhkkBEQEFDo8VXwQHhEsFhQ0CA4U8dYcXgzWHB4FhkX8YKYUfMC+CSgEBAQ X-IPAS-Result: AkACAHiVHVRKfVIrm2dsb2JhbABgg2FXBLhWj1iBa4dNAXQIFgERAQEBAQEGCwsJFCqEAwEBAQMBEi4BGxICCQEDAQsGBQsNDSEiAREBBQEKEgYTEhCIBwEDCQgNoQJtjSKDEIh0ChknAwpmhkkBEQEFDo8VXwQHhEsFhQ0CA4U8dYcXgzWHB4FhkX8YKYUfMC+CSgEBAQ X-IronPort-AV: E=Sophos;i="5.04,560,1406584800"; d="scan'208";a="80187476" Received: from mail-wg0-f43.google.com ([74.125.82.43]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 20 Sep 2014 16:59:45 +0200 Received: by mail-wg0-f43.google.com with SMTP id y10so1004469wgg.14 for ; Sat, 20 Sep 2014 07:59:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S3qnjm4EOiPi1baJJDM1xx0qrxLXGtcP6hFeiFCjT2Q=; b=S4P5OO5U0/XR8RvQ8nVE/mHn21kiEL0CEOZuMqH1awqMWNAcORXuwfUgWz73pKkzDC +fOyvB6pfYw1wDvPRhw6/2o8N9BtNVUVa2iMdFcgidP9zVgh2XtucFUxUnrx1F6Z1zsW pdi8KenzTltQ7ZqTtFRPs5cm+RYusF25wlFtGfado4TKjnj4tYW7mJgnLf1oYvWSC1AH SF3/VmAZ12tPjGXyQeNg1XqTkvTMZbhOBvGL87WdUFP/wBAxGlY9rNWff1dUV0aSnjIr BohmtUHpH3ONwon5yfUe/4huDQDquKcpSxeuRkkBtE00ajk2zFHc/0t70lgjLit3drGK ZPbQ== MIME-Version: 1.0 X-Received: by 10.180.99.163 with SMTP id er3mr633760wib.23.1411225185398; Sat, 20 Sep 2014 07:59:45 -0700 (PDT) Received: by 10.194.164.69 with HTTP; Sat, 20 Sep 2014 07:59:45 -0700 (PDT) In-Reply-To: <541B40CB.4050102@metaprl.org> References: <541B40CB.4050102@metaprl.org> Date: Sat, 20 Sep 2014 22:59:45 +0800 Message-ID: From: Jun Furuse To: Aleksey Nogin Cc: Caml List Content-Type: multipart/alternative; boundary=f46d041825a2dfb6f6050380777f Subject: Re: [Caml-list] improve omake [was One build system to rule them all] --f46d041825a2dfb6f6050380777f Content-Type: text/plain; charset=ISO-8859-1 Hi Aleksey, Quickly grepped the opam-repository, I am the one who has released the most packages require omake. I can be a maintainer, though I have no brilliant idea to enhance it for now... Jun On Fri, Sep 19, 2014 at 4:30 AM, Aleksey Nogin wrote: > All, > > As you obviously know, OMake have not had a proper maintainer for a few > years now - while I did not completely abandon it, I did not have time > to devote to even little things (like pushing out a new 0.9.8.6 release > which I have been hoping to call "version 1.0", and which have been > lingering in "release candidate" mode for almost four years). > > It is clear that there are quite a few people on this list with good > ideas on how to improve OMake (e.g. ability to write rules in OCaml > instead of/in addition to the OMake language seems like a good idea) - > so I am wondering - is there somebody who would be willing to take over > as the omake maintainer - ideally somebody whom people on this list > would trust with this role? > > If there was some sort of consensus on this list about a new maintainer, > I would be happy to pass on this role (redirect omake.metaprl.org > accordingly, etc). > > Aleksey > > > On 18.09.2014 13:14, Bob Zhang wrote: > > > Dear camlers, > > I have done some work to improve omake available here: > > https://github.com/bobzhang/omake-fork/tree/work > > Before deciding spending some time in improving omake, I have tried > > various build systems. > > 1. ocamlbuild > > ocamlbuild is really nice for small to medium projects and I have > > used it pervasively in my personal projects and corporation projects. It > > works pretty well in most cases. > > There are mainly three drawbacks: > > a. Easy things hard to do. > > Even for some very trivial things, if you don't write > > myocamlbuild.m for a long time, you have to google ocamlbuild API and > > figure it out how to do it correctly. > > b. Error messages hard to understand > > It's cool that ocamlbuild detect dependencies dynamically, when > > it does not work out, in general, I would turn on -verbose and search > > which part goes wrong. > > c. no parallellism > > This is fatal and main reason that I gave it up > > 2. ocp-build > > I tried it for my hobby project, it's not close to maturity yet. > > 3. jenga > > Jenga looks promising, but I don't think it would be usable inside > > our company, the dependency is huge, more importantly, its dependency > > chain includes Camlp4 which we can not rely on. Also, looking at the > > examples, it is quite verbose even for trivial projects. > > > > omake has its own drawbacks as well, for example, the language is > > overly complex and error message is hard to understand(still better than > > ocamlbuild), startup speed is slow, no easy FFI interface to write rules > > in OCaml language itself, but that's all we can find a way to fix. > > > > -- > > Regards > > -- Hongbo Zhang > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > --f46d041825a2dfb6f6050380777f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Aleksey,

Quickly grepped the opam-re= pository, I am the one who has released the most packages require omake. I = can be a maintainer, though I have no brilliant idea to enhance it for now.= ..

Jun

<= div class=3D"gmail_quote">On Fri, Sep 19, 2014 at 4:30 AM, Aleksey Nogin <= nogin@metaprl.org> wrote:
A= ll,

As you obviously know, OMake have not had a proper maintainer for a few
years now - while I did not completely abandon it, I did not have time
to devote to even little things (like pushing out a new 0.9.8.6 release
which I have been hoping to call "version 1.0", and which have be= en
lingering in "release candidate" mode for almost four years).

It is clear that there are quite a few people on this list with good
ideas on how to improve OMake (e.g. ability to write rules in OCaml
instead of/in addition to the OMake language seems like a good idea) -
so I am wondering - is there somebody who would be willing to take over
as the omake maintainer - ideally somebody whom people on this list
would trust with this role?

If there was some sort of consensus on this list about a new maintainer,
I would be happy to pass on this role (redirect omake.metaprl.org
accordingly, etc).

Aleksey


On 18.09.2014 13:14, Bob Zhang wrote:

> Dear camlers,
>=A0 =A0 I have done some work to=A0 improve omake available here:
>=A0 https://github.com/bobzhang/omake-fork/tree/work
>=A0 =A0 Before deciding spending some time in improving omake, I have t= ried
> various build systems.
>=A0 =A01. ocamlbuild
>=A0 =A0 =A0 =A0ocamlbuild is really nice for small to medium projects a= nd I have
> used it pervasively in my personal projects and corporation projects. = It
> works pretty well in most cases.
>=A0 =A0 =A0 There are mainly three drawbacks:
>=A0 =A0 =A0 =A0a. Easy things hard to do.
>=A0 =A0 =A0 =A0 =A0 =A0Even for some very trivial things, if you don= 9;t write
> myocamlbuild.m for a long time, you have to google ocamlbuild API and<= br> > figure it out how to do it correctly.
>=A0 =A0 =A0 b. Error messages hard to understand
>=A0 =A0 =A0 =A0 =A0 It's cool that ocamlbuild detect dependencies d= ynamically, when
> it does not work out, in general, I would turn on -verbose and search<= br> > which part goes wrong.
>=A0 =A0 =A0 c. no parallellism
>=A0 =A0 =A0 =A0 =A0This is fatal and main reason that I gave it up
>=A0 =A0 2. ocp-build
>=A0 =A0 =A0 =A0I tried it for my hobby project, it's not close to m= aturity yet.
>=A0 =A0 3. jenga
>=A0 =A0 =A0 =A0Jenga looks promising, but I don't think it would be= usable inside
> our company, the dependency is huge, more importantly, its dependency<= br> > chain includes Camlp4 which we can not rely on. Also, looking at the > examples, it is quite verbose even for trivial projects.
>
>=A0 =A0 omake has its own drawbacks as well, for example, the language = is
> overly complex and error message is hard to understand(still better th= an
> ocamlbuild), startup speed is slow, no easy FFI interface to write rul= es
> in OCaml language itself, but that's all we can find a way to fix.=
>
> --
> Regards
> -- Hongbo Zhang


--
Caml-list mailing list.=A0 Subscription management and archives:
ht= tps://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

--f46d041825a2dfb6f6050380777f--