Re: Applications in the Perl Group
Jonathan Yu <firstname.lastname@example.org> writes:
> Where a reusable module exists, that provides a command-line
> application (e.g. SQL::Translator/SQLFairy), we should have:
> 1. A source package called libsql-translator-perl
> 2. Produce two binary packages: sqlfairy and libsql-translator-perl
I'm not sure about this as it would mean the Packages file would grow
even more. Maybe a Provides: sqlfairy would be enough for most cases?
It would allow to use `apt-get install sqlfairy', but versioned
dependencies on the virtual package are not possible.
> Where an application exists (e.g. in the App::acme namespace), we should have:
> 1. A source package called acme
> 2. Produce a binary package called acme
> 3. If there is later some reusable component taken out of the original
> app, and distributed with the App package (e.g. other libraries now
> depend on this package), then we should also produce a
> libreusable-component-perl package.
I agree with this.