caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Gerd Stolpmann" <info@gerd-stolpmann.de>
To: "Adrien Nader" <adrien@notk.org>
Cc: "Francois Berenger" <berenger@riken.jp>, caml-list@inria.fr
Subject: Re: [Caml-list] opam and godi
Date: Mon, 22 Jul 2013 14:34:07 +0200	[thread overview]
Message-ID: <be499392263b5fcc10e22f581aab65ea.squirrel@gps.dynxs.de> (raw)
In-Reply-To: <20130722074657.GB10640@notk.org>


> On Mon, Jul 22, 2013, Francois Berenger wrote:
>> On 07/22/2013 03:55 PM, Fabrice Le Fessant wrote:
>> >Hello,
>> >
>> >   Looking only at the number of packages available in the
>> repositories,
>> >Opam has around 400 packages while Godi has around 170 packages. Also,
>> >Opam can use "aspcud" to compute the minimal number of changes when
>> >installing/updating, which can make a big difference when dependency
>> >constraints between packages become hard to solve. I also like the
>> >interface "à la apt-get", compared to the curses interface that I used
>> >with Godi.
>>
>> I also like the apt-get/aptitude style of OPAM command lines.
>>
>> As an impatient user, I also feel that OPAM is way faster than GODI.
>
> As far as I can tell, godi_console is now a native-compiled executable
> while it used to be byte-compiled before.
> This has made it *WAY* faster (at least 5 times faster according to my
> testing earlier). I really hated these 10-15 seconds of waiting.

Actually, this is fixed since I did a performance audit, giving special
attention to such problems. The natively-compiled command has always been
built, but the bug was that it wasn't installed :-(. Also, there is now
better caching of package scanning results.

Gerd
-- 
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.


  reply	other threads:[~2013-07-22 12:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51E40425.8060604@libertysurf.fr>
2013-07-15 14:20 ` [Caml-list] ocaml glade gtk3 r.3
2013-07-15 19:18   ` Martin DeMello
2013-07-19 17:22     ` [Caml-list] opam and godi r.3
2013-07-21 13:54       ` Gerd Stolpmann
2013-07-21 14:20         ` Anil Madhavapeddy
2013-07-21 14:43           ` Yaron Minsky
2013-07-22  7:44             ` Adrien Nader
2013-07-22 13:30               ` Anil Madhavapeddy
2013-07-22  8:06             ` Török Edwin
2013-07-22 12:20               ` Gerd Stolpmann
2013-07-22 12:55             ` Gerd Stolpmann
2013-07-22 18:30               ` Yaron Minsky
2013-07-22 13:51           ` David Scott
2013-07-22  6:55       ` Fabrice Le Fessant
2013-07-22  7:35         ` Francois Berenger
2013-07-22  7:46           ` Adrien Nader
2013-07-22 12:34             ` Gerd Stolpmann [this message]
2013-07-22  7:20       ` Matthieu Dubuget

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=be499392263b5fcc10e22f581aab65ea.squirrel@gps.dynxs.de \
    --to=info@gerd-stolpmann.de \
    --cc=adrien@notk.org \
    --cc=berenger@riken.jp \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).