[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new version of ocaml packages ...



On Thu, Dec 27, 2001 at 10:00:26AM +0100, Georges Mariano wrote:
> > Does not seems to me a valid point for break an almost standard
> > (there are a lot of perl package that follows this schema).
> Who said something like :
> "(but sure, we are packaging OCaml and not perl :)))"

:-)))))
but isn't again a valid point, a dh_ocaml.ml is a script that we
(package maintainer) use and we can write it in whatever language we
want, more over only the external interface (i.e. the command line) will
be seen by who use the script.
An "almost standard" works because a lot of user may have used perl (and
standard C libraries obviously) debian package and expect to find the
same structure in libraries naming schemas of other languages.

Most design guidelines said: "when nothing more helps, standardize!";
this means that no naming schemas is better that other in this case, so
just use the one that the user expect to find.

> > Think also about the pool structure, package that starts with "lib"
> > are kept in a separate tree, why you want that ocaml libraries will
> > not be included in this tree? A user knows that all libraries are
> > kept in the"lib" tree.
> 
> Simply, I would like to have ocaml stuff in the same tree ...
> I'm an ocaml user not a library user...
> Again, think different, we are NOT SOFTWARE we are  USERS ...

Here we have to think for all users not just for us, well in fact we are
probably the only debian ocaml users, but anyway ...
A user that knows a little of ocaml, but a lot of perl, in debian (a
user that, as you stated, is an _user_ and _not software_) looks for
libraries in the same manner that he looked in perl, so looking for
libxxx-ocaml.

Currently we have "ocaml-findlib", "ocaml-netstring" and "ocaml-doc" all
packages follows the same naming schema, but all of them are different
in kind! We also have "ocaml-tools" and "ocamltk"!
Surely changing "ocaml-netstring" in "libnetstring-ocaml" and "ocamltk"
in "libtk-ocaml" helps, next note that "libtk-ocaml" and "libtk-ruby"
are very similar, in fact they do the same thing only for different
languages.

Cheers.

-- 
Stefano "Zack" Zacchiroli <zack@cs.unibo.it> ICQ# 33538863
Home Page: http://www.cs.unibo.it/~zacchiro
Undergraduate student of Computer Science @ University of Bologna, Italy
                 - Information wants to be Open -

Attachment: pgpbJgJTDAcGw.pgp
Description: PGP signature


Reply to: