Re: please advice package names for padre plugins
Damyan:
Thanks for working on coordinating these packages, and thanks for
consulting the community about this issue.
I don't see anything wrong really with keeping in the current policy,
and thus naming them libpadre-plugin-foo-perl. Instead of
padre-plugin-<tab><tab> you'd just do libpadre.. etc.
On the other hand, since Padre itself is also released via CPAN and is
not named libpadre-perl, and rather is under padre, then I'd expect
that the plugins be made available under padre-plugin- etc.
I think, in general, judging from apt-cache's output when searching
for 'plugin':
If your package name is X
Then things that enhance your package should be called
X-Y
Where Y is some feature that it adds.
So: padre, should be enhanced by:
padre-plugins-. etc
This is my long-winded rationale, basically agreeing with Dominique on this.
Cheers,
Jonathan
On Wed, Jun 3, 2009 at 6:05 AM, Damyan Ivanov <dmn@debian.org> wrote:
> (sorry for nt sending this mail earlier, RL keeps me busy)
>
> Hi,
>
> Ryan has started work on packaging plugins for Padre -- the killer
> editor for Perl and other code :) Thanks, Ryan!
>
> We were wondering how to name the packages. There are two
> possibilities:
>
> * libpadre-plugin-foo-perl
> + all the plugins are available via CPAN and are perl modules.
> + this is what Perl policy mandates
>
> * padre-plugin-foo
> + these modules are intented to be used as Padre complements, adding
> new features to it
> + they have limitted (it not void) use outside of Padre
> + a bit easier finding (apt-get install padre-plugin<tab><tab>)
>
> What would you use?
>
> --
> dam
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkomSwIACgkQHqjlqpcl9jsAFQCfY57srwbjoWmO70iPuUFK3fcT
> YocAnR/36Jqgvqq3uSZlGRrgOlGtRxX0
> =qphU
> -----END PGP SIGNATURE-----
>
>
Reply to: