[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#748535: Bug#764098: gst-plugins-bad0.10: build-depends on libgnutls-dev



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

[ About the benefit of requiring a sourceful upload of reverse b-d,
  instead of providing the libgnutls-dev by the accurate package. ]

Le 05/10/2014 12:35, Andreas Metzler a écrit :
> On 2014-10-05 David Prévot <taffit@debian.org> wrote:
>> On Sun, Oct 05, 2014 at 04:11:44PM +0200, Andreas Metzler wrote:

>>> GnuTLS 2 and 3 are not completely API compatible. And given that this
>>> transition is basically finished […], I would like to keep the small
>>> benefit of having this incompatibility reflected in the package name.

>> Indeed, the benefit seems rather small compared to making all further
>> gnutls transition more painful by forcing all of its reverse b-d to
>> provide a sourceful upload instead of triggering a simple binNMU when
>> possible.
> 
> I think there is small misunderstanding: The fact that we now have
> libgnutls28-dev does not mean that we will have matching versioned
> development packages (libgnutls{30,31,31,etc}-dev) for the library
> package (libgnutls{30,31,31,etc}) in later versions. There is no
>  reason why future gnutls transition should be hurt by the current naming of
> the gnutl development package.

I don’t deny there is a misunderstanding, but I’m not sure how small it
is. I don’t get either the benefit of having “28” somewhere in the name
to make it clear that the package is about GnuTLS 3 (or any later version).

Anyway, documenting those concerns in the transition bug report since
they don’t seem to have been raised before.

Regards

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJUMYe9AAoJEAWMHPlE9r08yQ0IAI7XDrlXTpzVmXl8gP/6FqAu
nUfgaCPvfOLxPzK9VSRswLLPfzVmvQ3cWko7sEnA4lqD6Q3AhdETVEOwCXPu/qqT
polrrU7btBBkoG7/2LL2g0nxMXOm6zof7MHsW590mgXS6e5e/GGUlF7WqKipasBf
ZytxJyIHHeO1p1XZkQwfgTgDmTgdBSDIKrtseDYk+ElDkNWVM1ShP1gU2y/cCIVI
tWJEUgKd6vyd6p9SrLpVZ2ymKLrhs/8QsoZsBzSCvQ63MgxV9kcbWJNN8UE0OOeJ
xqGdcGT9QPxHSggHuBiaa+XfmGpZtomqGCV2gjqt3TPp2d0UF5Yv2U8WlDzpebw=
=Qplw
-----END PGP SIGNATURE-----


Reply to: