On Fri, Dec 14, 2001 at 03:53:49PM +0100, Stefano Zacchiroli wrote: > On Fri, Dec 14, 2001 at 03:02:08PM +0100, Sven wrote: > > mmm, i thought to use the less strong of the two, i suppose that is suggest, > > will have to check ? > > the less strong is suggests. > > > > > o i am not sure about splitting off a camlp4 package ? > > > the binary package is sized 4Mb so probably is a good idea. > > > > Yes, but i will have to master the multi package stuff first :))) > > good luck :) > > > > mainly, that all is stuff have not to be done before freeze. > > > This involve a lot of package updates and is better to delay it after > > > woody. > > mmm, all these packages will have to be rebuilt for ocaml 3.04 anyway. > > yes, but rebuilding is less error prone. IMO we can't take the risk to > freeze packages will problems (remember that we, the debian ocamlers, > are a small community and a bug may exists and not be reported for a > long time ...). > I also think that is nice to freeze ocaml packages that are almost > similar in organization, if we want split now we take the risk thas some > libraries will be freezed splitted and some other not. > > > > [ Minor: probably we have to start thinking about write an > > > ocaml-debian-policy like, the python-debian-policy. I.e. a set of > > > guidelines for packaging ocaml sw in debian ] > > > > Yes, i was thinking about something such, were does such a policy need to be > > sent once it is written ? > > don't know, probably on this list :-) > Seriously, when we want to do it we can ask the python guys, I think > anyway that such a policy will not be mandatory as the debian-policy, > but just a set of guidelines for debian ocamlers. > > > compiled once for all arch by its maintainer) and he can install the -native > > version if available if he wants to do -native developpment. Needless to say > > ok, but on the average I think that none want to do only bytecode > developmente if they can do both development, anyway this is just a > personal opinion.
Well, it would be nice to split away the stub libraries into a separate package, so people could install them and run dynamically linked bytecode executables. Friendly, Sven Luther
