Hi Thomas, Thomas de Grenier de Latour <[EMAIL PROTECTED]> writes:
> - I had to change "equeue" into "equeue-core" for the EQUEUEDIR > declaration in the Makefile, since that's where the module > contents actually is here (with equeue-2.0.1). > In /usr/lib/ocaml/equeue, all I have is a META file, with > "equeue-core" in the requires. I'm not sure exactly, but there is > probably something here that ocamlfind could solve automagically. > Something like this should follow the requires and output in > "-I /path/to/equeue -I /path/to/equeue-core" format: > EQUEUEFLAGS:=$(shell ocamlfind query -i-format -recursive equeue) > I think that in general, it would be a good idea to switch to > such recursive queries in the Makefile or future configure > script, cause it would also solve issue where some modules deps > are missing (like in a previous version where i had to add expat > or curl to the Makefile depending how cduce was compiled). Yes, using -i-format -recursive options to ocaml find is a good idea. In fact, I've never digged into ocamlfind documentation. I have added this to my TODO list. About equeue-core, it does not seem to be needed on my debian system. Equeue version is 2.1. I can't tell more. > - I've had to add "-I /usr/lib/ocaml/site-packages/stublibs" to > the CLNT_OCAMLINC, otherwise compilation was failing with: [...] > Error on dynamically loaded library: dllmlgz.so: cannot open > shared object file: No such file or directory > make: *** [gtk2-clnt/demexp-gtk2-client.bc] Error 2 > ---------------------------------------------------------------- > It sounds strange to explicitly include this dir, i would have > thought it was in some kind of default path or something. I don't > know what would be the clean fix here, maybe that's also > something where ocamlfind could help, or maybe it's a > Gentoo/Ocaml issue. On Debian, is this directory in the > /etc/ld.so.conf or something like that? Once again, I don't have such issues on my debian system. Maybe a Gentoo/OCaml issue. > If you really want improvement requests, one item i would add to > your TODO is a logging system for the server: it would be nice if > it could have at least a "--logfile /path/to/logfile" option > (because right no, to get a logfile while launching it via > start-stop-daemon, i must use a wrapper shell script to make the > stdout/stderr redirection, and that's not really beautiful). Ok, I've added this to my TODO. > And sure, all the other features of a unix daemon (taking care > of its pid file, a new file "bases.pid" is now created in latest dev version. > dropping privileges, No need for this as the server does not use any privilege. However, it might be useful to have a "demexp" account specific for the server and to give appropriate rights to the server files. I leave this to package maintainers. :) > detaching to background, I have added this to my TODO. > Oh, and one last very simple request: there is much valuable info > in your 0.6 announcement text, so don't forget to include it > somewhere in the source tarball so that packages can install a > copy in /usr/share/doc :) Yes, it is already in the source tree. :) > Maybe you could put the .schemas file and this short explanation > in the misc/ directory, it may be useful for other packagers. Yep, good idea. One more TODO item. > As for the URI vs. URL distinction, eh, i don't really know what > the difference is, so i randomly use one or the other. > `wtf` doesn't help much here: > % wtf url > url [uri] (7) - uniform resource identifier (URI), > including a URL or URN > > Go figure... According to http://www.w3.org/Addressing/URL/uri-spec.html , an URI is a name in a namespace. On the contrary, an URL gives more concrete information to use a given protocol (e.g. server name and port). So, currently demexp:// are URL. When we will have distributed and interconnected servers, we will have URI (or URN ? ;). Thank you for your feedback. Yours, d. -- pub 1024D/A3AD7A2A 2004-10-03 David MENTRE <[EMAIL PROTECTED]> 5996 CC46 4612 9CA4 3562 D7AC 6C67 9E96 A3AD 7A2A _______________________________________________ Demexp-dev mailing list Demexp-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/demexp-dev
