Manoj Srivastava wrote: > On Thu, Sep 03 2009, Franck Joncourt wrote: >> At a first glance there is no need to split it, and all of the binary >> packages could be created from one source package as you mentionned. >> However, for other distributions than Debian I do not know how their >> packaging stuff work. > > This is not an issue for any Debian derivatives; they all take > the same underlying package infrastructure. Non derivative > distributions will not use the Debian packaging, and thus splitting it > in Debian will not help anyone. > > So, if this is questions the upstream is considering, you > already have the answer: > >> Looking at projects like mysql and dhcp, I would tend to say it is fine >> to have both the client and server applications bundled in the source >> package with the shared library. > > I think the project, and thus the tarball, should reflect the > line of development; this is a single project, developed together, and > thus the tarball should remain together, especially since this avoids > the hassle of the different source tarballs gtting out of sync > somewhere. > > Most distriutions have already figured out how to create > multiple binary packages from a single source tarball, so this should > not be a consideration. Thanks for your answer. Upstream is going to work with a single tarball ; There was a misunderstanding between tarballs and binary packages. At least, it is now clear :) Regards, -- Franck Joncourt http://debian.org - http://smhteam.info/wiki/
Attachment:
signature.asc
Description: OpenPGP digital signature