Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Thomas Fischbacher <t.fischbacher@soton.ac.uk>
To: Mehdi Dogguy <mehdi.dogguy@pps.jussieu.fr>
Cc: Martin DeMello <martindemello@gmail.com>,
	OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] adding a scripting language to an ocaml program
Date: Thu, 8 Jul 2010 16:22:49 +0100	[thread overview]
Message-ID: <4C35ED49.3050808@soton.ac.uk> (raw)
In-Reply-To: <4C321E33.1000301@pps.jussieu.fr>


Mehdi Dogguy wrote:

> 	http://lists.debian.org/debian-ocaml-maint/2007/11/msg00158.html
> 
>> Replacing the code in the debian package with ours is quite 
>> straightforward.

Well... I just updated the directory at:

  http://www.soton.ac.uk/~doctom/software/pycaml-patched/

When I debuild -us -uc the lot, this produces a working package
on my machine.

> … if the interface is "compatible" (I didn't really check). 

I think so. Basically, I removed one function which never had worked
anyway and added a number of new ones.

> I had a
> quick look and noticed some changes for some type definitions. Did you
> try to compile coccinelle¹ using your version of pycaml for example?

I just gave it a try - please take a look at the log at:

http://www.soton.ac.uk/~doctom/software/coccinelle.log

> It's the single package using the pycaml library we have in our
> archive. If it requires some changes, we'd prefer to get them integrated
> by coccinelle's upstream before shipping the new pycaml.
> 
> ¹: http://coccinelle.lip6.fr/
> 
> Besides, having a version and listable directory with available versions
> of pycaml would help to get the code packaged and integrated. Would you
> accept to maintain it on forge.ocamlcore.org? We can provide you a
> D?$VCS, a bugtracker, etc… there. If yes, please fill the form available at:
> 
> 	https://forge.ocamlcore.org/register/projectinfo.php

Yes, we could (and should) do that.

I'm just waiting for the account registration confirmation email.

-- 
best regards,
Thomas Fischbacher
t.fischbacher@soton.ac.uk


  reply	other threads:[~2010-07-08 15:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 18:34 Martin DeMello
2010-07-03 18:43 ` Michael Ekstrand
2010-07-03 18:56   ` [Caml-list] " Martin DeMello
2010-07-03 19:06     ` Michael Ekstrand
2010-07-03 19:35     ` [Caml-list] " David Allsopp
2010-07-03 18:52 ` [Caml-list] " Lukasz Stafiniak
2010-07-03 18:53   ` Vincent Aravantinos
2010-07-03 19:05     ` Martin DeMello
2010-07-03 19:02   ` Martin DeMello
     [not found]     ` <AANLkTinIbSSrxtuWrwv16_XIo2MU2hdhjHhrIORSFUPN@mail.gmail.com>
2010-07-03 21:15       ` Martin DeMello
2010-07-03 20:42   ` malc
2010-07-03 19:16 ` David Powers
2010-07-04 19:54 ` Goswin von Brederlow
2010-07-05 12:41   ` Florent Monnier
2010-07-05 13:14 ` Thomas Fischbacher
2010-07-05 16:13   ` Mehdi Dogguy
2010-07-05 16:30     ` Thomas Fischbacher
2010-07-05 18:02       ` Mehdi Dogguy
2010-07-08 15:22         ` Thomas Fischbacher [this message]
2010-07-08 16:00           ` Mehdi Dogguy
2010-07-06 21:01       ` Guillaume Yziquel
2010-07-06 21:08         ` Guillaume Yziquel
2010-07-06 10:38 ` Richard Jones
2010-07-06 12:55   ` Martin DeMello

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=4C35ED49.3050808@soton.ac.uk \
    --to=t.fischbacher@soton.ac.uk \
    --cc=caml-list@yquem.inria.fr \
    --cc=martindemello@gmail.com \
    --cc=mehdi.dogguy@pps.jussieu.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