[Daniel Baumann] > > And I doubt the release > > team would accept it, anyway. Lenny is frozen. > > i don't think the release team is that unreasonable to now allow a feeze > exception for it. The library freeze was about 2 months ago. I don't think the release managers would want to let a library package go through NEW now and _still_ make it into lenny. There is also the practical problem of splitting a library into 2 builds. They either have to conflict with each other, or they have to use different SONAMEs. And somehow an application has to get the appropriate dependency, which pretty much means two separate -dev packages, so packages can Build-Depends on the specific one they want. (See libneon27 / libneon27-gnutls, for example.) What a mess. I don't think any of that is appropriate for lenny at this time. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
Attachment:
signature.asc
Description: Digital signature