Your message dated Thu, 26 Jan 2023 20:55:51 -0500
with message-id <[email protected]>
and subject line 
has caused the Debian Bug report #726571,
regarding RlwrapFilter.pm should be /usr/share/perl5/App/Rlwrap/Filter.pm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
726571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rlwrap
Version: 0.37-3
Severity: wishlist

        The conventional namespace for application-specific Perl modules
        is App::⟨package name⟩::⟨module name…⟩.  Moreover, the
        conventional directory for Perl modules is /usr/share/perl5, and
        indeed, – it’s already in @INC, while /usr/share/rlwrap isn’t.

        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.)

use lib ($ENV{RLWRAP_FILTERDIR} or ".");
use RlwrapFilter;

        AIUI, the non-standard RLWRAP_FILTERDIR becomes completely
        unnecessary after the change, but may be retained for
        compatibility with the filters following the current convention.

-- 
FSF associate member #7257

--- End Message ---
--- Begin Message --- The issue listed here is beyond old, and as was stated this should be followed up with Upstream and not as a delta in the package.

Closing this bug.

--- End Message ---

Reply via email to