Iustin Pop wrote: > The main reason I chosed to have a single library package was to not > have too many small packages, and per the above thread, upstream > "intends" to keep them in sync. Also, libprotoc is/should only be used > by the protobuf compiler, and not by external users, so I thought > shipping it in the libprotobufX package is fine.
libprotoc is used by the protobuf-c compiler, protoc-c. protobuf-c is not (yet) in debian. > As far as I can understand, your point is that upstream is never > guaranteed to do so, and in order to prevent future problems it's better > to split the packages? > > I also see other library packages providing multiple libraries (e.g. > libssl0.9.8), so how "hard" is this rule? it is not a particularly hard rule but the trend in debian has been towards less aggregation in library packages, not more. -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
