❦ 13 novembre 2013 05:30 CET, Tom Lee <debian@tomlee.co> :
> I work on the packaging for capnproto.
>
> Upstream has provided a new source tarball that introduces a new shared
> library (libkj). Theoretically, this shared library is stand-alone & could
> be used independently, but it is likely only interesting to users of
> capnproto in the short term.
>
> In the developer's words:
>
> "It can exist independently, and some day it might be "marketed" as a
> separate library. For now, though, it is bundled with Cap'n Proto and used
> only by Cap'n Proto users. Unless Debian mandates breaking these out or we
> actually see some demand for KJ being separate, I don't think we need to
> divide the package yet."
>
> I *think* I should extract libkj as a separate binary package & am
> currently proceeding under that assumption, but thought I'd ask here RE:
> whether I'm correct. Do I really need to split out libkj at this time?
No, you don't. Is the versioning the same?
--
10.0 times 0.1 is hardly ever 1.0.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature