<asmanur>
gildor: I guess I can get more visibility there anyway
<gildor>
asmanur: indeed, I don't know of your project at all
<gildor>
asmanur: if it where on the forge I would have now it
<gildor>
(or if you have somehow blogged about it)
<avsm>
does the forge have easy git access?
<mfp>
asmanur: if you are working on it, it's probably a better foundation that my markup hack (which I just wrote to scratch a personal itch for ocsiblog)
<mfp>
*than
<asmanur>
mfp: yep, i've been working on it since one year (not full-time though)
<gildor>
avsm: you have git+ssh and anonymous access
<gildor>
avsm: + gitweb
<asmanur>
s/since/for
<gildor>
avsm: but it is not as beautiful as github or gitorious
<avsm>
i find developing on github is really convenient (as i just have to deal with one site). but mirroring ocaml projects to the forge might be quite convenient
<avsm>
*as well
julm_ has joined #ocaml
<gildor>
avsm: yes, this is what batteries do and I think it is a good way to get the best of git on the one hand and a good visibility in the ocaml community on the other hand
<gildor>
mfp: so you think I should use asmanur's mldown
<gildor>
asmanur: you got a lot of "Warning P: this pattern-matching is not exhaustive."
<asmanur>
gildor: indeed :D
<asmanur>
gildor: this is mainly in old backends
<asmanur>
that are currently used by virtually nobody
<asmanur>
as the AST grows I didn't want to bother to extend them
<gildor>
asmanur: you should not play with ocalmfind -destdir ...
<asmanur>
hm
<asmanur>
gildor: yep my install script is quite buggy, it's my first real project with an install script actually
Associat0r has joined #ocaml
<gildor>
-destdir $(ocamlc -where) will force ocamlfind to install in a non-default directory for him
<asmanur>
I had to to this otherwise it was not found iirc
<gildor>
asmanur: want an OASIS setup? for this
<asmanur>
yep that would be nice :)
<gildor>
asmanur: if you don't set -destdir on the command people can override it using the environment varialb eOCAMLFIND_DESTDIR=/home/gildor/programmation/00build/ocaml-3.11.2-linux-amd64/lib/ocaml/
<gildor>
for example
<asmanur>
ok
<gildor>
I can provide you with a _oasis + a working setup
<gildor>
but you'll need to wait OASIS 0.2.0 to be able to have a setup-dev (i.e. a setup that auto-update when you add modules/options to _oasis)
<asmanur>
ok
<asmanur>
but is oasis ready to use yet ? last time I checked it wasn't
julm_ has left #ocaml []
<gildor>
asmanur: what was your problem last time you checked?
julm has joined #ocaml
<asmanur>
hm
<gildor>
asmanur: GPL 3, is it on purpose?
<asmanur>
there were no official release
<asmanur>
hm
<gildor>
since april there is a 0.1.0 release
ttamttam has joined #ocaml
<gildor>
it has bugs but it works enough well
<asmanur>
ok :)
<asmanur>
well I hesitate between GPL and LGPL
<gildor>
the 0.2.0 release is far better
<gildor>
asmanur: for OCaml projects, we generally prefers LGPL + OCaml linking exception
<mfp>
gildor: I haven't seem asmanur's code and don't know what he intends to do, so I can't really say. If he plans to work on it and implement all of markdown, probably.
<gildor>
GPL for a library is quite strong
<asmanur>
yes
<asmanur>
maybe I'll switch to LGPL
<mfp>
my code works and the more-markdown-compat branch approaches markdown, but I have no plans to work on it in the near future
<gildor>
asmanur: you can handle README.text with mldown ?
<asmanur>
it's not "markdown" actually it's mdown but the syntax is very close
<gildor>
what is the difference ? (any URL?)
<gildor>
asmanur: you seems to have things in common with pandoc, is it on purpose ?
<asmanur>
gildor: mdown is a spec designed by a friend of mine, there is a spec but it's more complicated than markdown and I implement only a major subset
<asmanur>
gildor: I don't know about pandoc but it seems that they basically do what I do
Vassia has joined #ocaml
<gildor>
asmanur: have you a kind of compatibility with markdown?
<asmanur>
gildor: yes
<gildor>
I see that you can use the Parser markdown
<asmanur>
there's two frontend, markdown and mdown,
<gildor>
I will probably use the markdown frontend
<asmanur>
the markdown is not I think fully compatible with the the original implementation
<asmanur>
but it's more a matter of testing than really a major issue
<gildor>
asmanur: you would accept patches on the markdown part to make it more compliant ?
<asmanur>
For now the frontend should be "good enough" to parse any typical data that don't use complicated and nested expressions
<asmanur>
gildor: yes!
<asmanur>
I hope the frontend can be hacked easily
<gildor>
asmanur: ok, I will see how well it integrates with my needs
<asmanur>
gildor: do you need an ocsigen integration by the way ?
<gildor>
asmanur: yes
<asmanur>
I have started a mldown_eliom module
<asmanur>
(was not too sure how to integrate it with the repo)
<gildor>
if you want the long story, I will use your library to parse _oasis description and display it on oasis.ocamlcore.org (the hopefully future OCaml CPAN)
<asmanur>
ok
<gildor>
is you mldown_eliom module ready for release ?
<asmanur>
hm
<asmanur>
not completely
<asmanur>
there's still an Obj.magic to bypass Eliom's XHTML.M module because mldown's AST do not forbid "links in links" for instance
Vassia has quit [Ping timeout: 276 seconds]
<gildor>
let me test your mldown parsing and integration
<asmanur>
ok
<gildor>
asmanur: you don't need directory = "+mldown" when you install the META file in the same directory as your library
<asmanur>
ok
ygrek has quit [Remote host closed the connection]
ygrek has joined #ocaml
jakedouglas has quit [Quit: Leaving.]
dmhouse has joined #ocaml
<asmanur>
gildor: I fixed the install script and the META file along with some warnings.