On Wed, Oct 16, 2013 at 18:56:33 +0000, Ivan Shmakov wrote: > The conventional namespace for application-specific Perl modules > is App::⟨package name⟩::⟨module name…⟩.
Can you give some examples or references? I see a few but not enough that I'd call it a convention. As opposed to simply $PACKAGE::$MODULE... > Moreover, the > conventional directory for Perl modules is /usr/share/perl5, and > indeed, – it’s already in @INC, while /usr/share/rlwrap isn’t. This is indeed required for packages that primarily provide perl libraries. However there are also many packages in Debian that install perl modules in application-specific directories when those modules are primarily for that application's use only. > Therefore, my suggestion would be to move RlwrapFilter.pm from > /usr/share/rlwrap to /usr/share/perl5/App/Rlwrap/Filter.pm, and > edit its ‘package’ line (as well as the filters’ ‘use’ lines) > respectively. (In order to preserve compatibility, a > “redirecting” .pm may be installed at the former location.) > > This will bring the module in line with the other Perl modules > in Debian, and will allow for a Perl filter to be started with > simple ‘use App::Rlwrap::Filter;’ instead of the current form, > which explicitly the Perl module search path (as shown below.) Do you have any other reasons for wanting to make this change, some added functionality or benefit that would come from doing this reorganization? -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
