request for packaging

[Kilian Krause]

--=-/V6eTWIjS9ypZErdcfvc
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Hi Jose,

Am Dienstag, den 28.12.2004, 21:34 +0100 schrieb Jose Carlos Garcia
Sogo:
> El mar, 28-12-2004 a las 00:02 +0100, Kilian Krause escribi=F3:
>=20
> > > please don't do that, keep the package in one piece.
> >=20
> > we'll be piecing it together like your desire was above combined with
> > what the policy does force us to do. Yet don't worry about the lib bein=
g
> > split out. Debian isn't like other distros where more dependencies are =
a
> > bad thing to have.
>=20
>  Yes, but we shouldn't create new packages if they are not strictly
> necessary. Packages file size is being a problem now for people with
> slow connections (like me for these days), or with old hardware. So
> basically we need to create the number of packages that are needed. And
> think that splitting a very tiny library in one package only because an
> admin can think on using it alone can be a bit overkill (I don't know if
> that's the situation for these libs). Disk space and bandwith for the
> download he is going to make is much cheaper than the increase on size
> in Packages file for *everybody*.
>=20
>  Of course, if those libs have different sonames, and change different
> across releases, we would probably want two different packages.

if we want both a client and a server package, i don't see any other way
than forming a "yate-common" package with the backend infrastructure for
both to depend on. From this point i'm much more convinced that
including more modules is better than forcing the admin-gui into the
daemon package. I haven't double checked, but so far the backend is the
lib plus it's .yate files IIRC. Thus creating a -common package would
only contain a *.so file and thus be technically a lib and should be
named accordingly.

--=20
Best regards,
 Kilian

--=-/V6eTWIjS9ypZErdcfvc
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBB0ytlvdkzt4X+wX8RAps5AJ4lBVrxDg3ErIVahBDotw1y8lmFcgCfb7eR
sNvIukSEB6uVJt16IQ4T0jA=
=I31N
-----END PGP SIGNATURE-----

--=-/V6eTWIjS9ypZErdcfvc--