Daniel said: > > I don't see what I can really do about this. Dropping the static > > libraries entirely would be a policy violation, and compiling static > > libraries which contain just one big .o file wouldn't be much better.
Reading policy about static libs[1] says "The static library (libraryname.a) is usually in addition to the shared version", which doesn't sound like a requirement. More importantly, what real life use static kdepim libraries when there are no static libs for the underlying libraries? In other news, kdepim not getting compiled is getting a showstopper on our "kde 3.3 for sarge, please" quest. [1] http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static
