Le 26/01/2012 11:24, Hendrik Tews a écrit : > It looks like a hostile takeover, and you cannot do that without the > maintainer's agreement unless the package is orphaned. > > No, no hostility intended. It was only that at first, I didn't > see your reply from January 19 (because it was debian-ocaml-maint > only). I therefore thought it would be best if I go ahead and > prepare a package. Only after I announced my package I saw your > replay in the debian-ocaml-maint archives.
I recommend you to subscribe to debian-ocaml-maint. > OK, I now understand that you want to keep otags in the git > repository. What should I do in order to obtain write access > there? Ask for membership to pkg-ocaml-maint on Alioth. I recommend you to have a look at [1]. [1] http://wiki.debian.org/Teams/OCamlTaskForce/ > As Ralf said, "camlp4-extra (>= 3.12.1), camlp4-extra (< 3.13.)"... but > why do you want the "< 3.13" part? > > Otags works on the internal abstract syntax tree. It has to be > changed with every major release. My new otags contains the > camlp4 parsers internally. It is very likely that they will > produce syntax errors with 3.13 sources. Further, with > non-standard syntax extensions, otags uses an external camlp4 for > parsing, which sends the ast back as marshaled value (printer > DumpCamlp4). This cannot work with a different major version. I don't see the point of putting this check in dependencies (or in ./configure for that matter). It puts a useless burden on whoever will update the package. An explicit failure pointing directly at what needs to be fixed is much more useful IMHO. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-ocaml-maint-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f213c6d.3060...@debian.org
