Re: MBF alert: packages with very long source / .deb filenames

[Jaldhar H. Vyas <jaldhar@debian.org>]

gregor herrmann <gregoa <at> debian.org> writes:

> As far as I understand source format v3 with multiple upstream
> tarballs, the first part (up to .orig) can't be changed as it needs
> to be the same as for the "main" package. [0] The second part (the
> component) name is free-form, and as I said earlier, here's a bit of
> room for us to shorten it (in this case e.g. from
> CGI-Application-Plugin-ValidateRM-2-3 to ValidateRM).
> 

But that doesn't preserve the upstream tarball name which in general I think you
would want to do.  Anyway that is why I did it that way originally.

> Cheers,
> gregor
> 
> [0] Although in this case the package name itself is made up and
> could be shortend from libcgi-application-basic-plugin-bundle-perl to
> something like libcgi-application-plugins-perl.
> 

Note that there is an extra-plugin-bundle too.  The dividing line is that
"basic" plugins are (upstream) dependencies of Titanium.

This whole thing was an experiment in the new source format but it is
increasingly looking like more trouble than it is worth.  Let's just split it up
into individual module packages.