On Fri, Mar 04, 2016 at 12:42:53AM +0100, Jonas Smedegaard wrote: > Quoting Christian Hofstaedtler (2016-03-03 22:47:48) > > May I suggest dropping the exact ruby version from the package name, > > so it doesn't have to go through NEW for 2.4, 2.5, ...? > > > > I see uwsgi-plugin-rbthreads already doesn't encode the version in the > > package name. > > You sure may suggest it (explicitly too - was arguably already > implicitly hinted at by the bugreport), and yes there is indeed > inconsistency across the uwsgi packages. > > The aim is, however, the opposite: For each library with multiple > concurrent versions - even if only a single of them reaching stable at > any point in time - have correspondent uwsgi packages (and then > additionally have a convenience package linkest against current "main" > version). I insist: please stop doing that. This unecessarily slows down the Ruby transitions as uwsgi cannot be just binNMUed to be updated. There are other 130 packages with Ruby native extensions that work just fine with a single Ruby package providing the native libraries for the currently supported Ruby versions in a single binary package. Ah and it also wastes FTP master time when processing binNEW. -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: PGP signature