tags 500036 + confirmed thanks On Wed, Sep 24, 2008 at 03:36:13PM +0200, Stephane Glondu wrote: > More pragmatically, since we will most likely have to handle generation > of .cmxs ourselves (i.e. in packaging process), I don't suggest to > massively and systematically move .cma/META files in all existing > packages, but rather do it in a as-needed basis (note that I used the > verb "allow" in this report). The policy should state the possibility, > though.
As discussed with Stephane, I concur with this request. Some more thoughts on the topic. - Ideally, with the advent of 3.11, we would probably want to _systematically_ move all dynamically-loadable objects to the runtime part of libraries. On the other hand, that would require quite a lot of work, and we don't know yet whether the practice of dynamically loading will become widespread or not. In the interim just allowing the possibility is a good compromise. - I believe (but it needs to be checked) that the current policy mandates to have dependencies from -dev packages to their runtime counterpart, if any. This enables smoothly migrating dynamically-loadable objects from -dev packages to runtime packages without breaking dependencies. - We should also allow in policy to have META files in runtime library packages. A good way to write that down is probably to state that the META file must be available when a -dev package is installed, observing that this can happen either because the -dev package is shipping the META file or because some of its dependencies is. Thanks for this reminder-bugreport. Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/ I'm still an SGML person,this newfangled /\ All one has to do is hit the XML stuff is so ... simplistic -- Manoj \/ right keys at the right time
signature.asc
Description: Digital signature
