Bug 202833 - devel/p5-Term-ReadLine-Perl conflicts with devel/p5-Term-ReadLine
Summary: devel/p5-Term-ReadLine-Perl conflicts with devel/p5-Term-ReadLine
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-perl (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-02 12:35 UTC by freebsd
Modified: 2022-03-10 07:10 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description freebsd 2015-09-02 12:35:41 UTC 
If devel/p5-Term-ReadLine is already installed then its ".packlist" causes conflict with devel/p5-Term-ReadLine-Perl ...

...
===>  Installing for p5-Term-ReadLine-Perl-1.0303_1
===>  Checking if p5-Term-ReadLine-Perl already installed
===>   Registering installation for p5-Term-ReadLine-Perl-1.0303_1
Installing p5-Term-ReadLine-Perl-1.0303_1...
pkg-static: p5-Term-ReadLine-Perl-1.0303_1 conflicts with p5-Term-ReadLine-1.14_1 (installs files into the same place).  Problematic file: /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/.packlist
*** Error code 70

Stop.

... which is just puzzling, given that rather inconsequential ".packlist" that causes conflict but not any of /working/ (doc included) components ...

# pkg info -l devel/p5-Term-ReadLine
p5-Term-ReadLine-1.14_1:
        /misc/local/lib/perl5/site_perl/Term/ReadLine.pm
        /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/.packlist
        /misc/local/lib/perl5/site_perl/man/man3/Term::ReadLine.3.gz
        /misc/local/share/licenses/p5-Term-ReadLine-1.14_1/ART10
        /misc/local/share/licenses/p5-Term-ReadLine-1.14_1/GPLv1
        /misc/local/share/licenses/p5-Term-ReadLine-1.14_1/LICENSE
        /misc/local/share/licenses/p5-Term-ReadLine-1.14_1/catalog.mk

# pkg info -l devel/p5-Term-ReadLine-Perl
p5-Term-ReadLine-Perl-1.0303_1:
        /misc/local/lib/perl5/site_perl/Term/ReadLine/Perl.pm
        /misc/local/lib/perl5/site_perl/Term/ReadLine/readline.pm
        /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/.packlist


EXPECTED RESULT is that I should be able to install both modules.


To REPRODUCE, first install devel/p5-Term-ReadLine; then try to install devel/p5-Term-ReadLine-Perl.


SOLUTION should be that newer entries should be appended to already existing ".packlist". (I am not familiar with ".packlist" use, other than expecting that recently added modules are appended & any removed ones are rarely deleted via cpan(m|plus) command(s).)
Comment 1 freebsd 2015-09-02 12:46:22 UTC 
I was going to suggest to install .packlist of p5-Term-ReadLine-Perl in */Term/ReadLine/Perl/ directory, but was not sure previously. After installing p5-ReadLine-Gnu I see that that had some validity after all ...

# pkg info -l devel/p5-ReadLine-Gnu
p5-ReadLine-Gnu-1.26:
        /misc/local/bin/perlsh
        /misc/local/lib/perl5/site_perl/mach/5.20/Term/ReadLine/Gnu.pm
        /misc/local/lib/perl5/site_perl/mach/5.20/Term/ReadLine/Gnu/XS.pm
        /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/Gnu/.packlist
        /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/Gnu/Gnu.so
        /misc/local/lib/perl5/site_perl/mach/5.20/auto/Term/ReadLine/Gnu/XS/autosplit.ix
        /misc/local/lib/perl5/site_perl/man/man3/Term::ReadLine::Gnu.3.gz
        /misc/local/man/man1/perlsh.1.gz
        /misc/local/share/licenses/p5-ReadLine-Gnu-1.26/ART10
        /misc/local/share/licenses/p5-ReadLine-Gnu-1.26/GPLv1
        /misc/local/share/licenses/p5-ReadLine-Gnu-1.26/LICENSE
        /misc/local/share/licenses/p5-ReadLine-Gnu-1.26/catalog.mk
Comment 2 Walter Schwarzenfeld 2018-01-12 22:31:52 UTC 
pkg-plists shows

devel/p5-Term-ReadLine
%%PERL5_MAN3%%/Term::ReadLine.3.gz
%%SITE_PERL%%/Term/ReadLine.pm

devel/p5-Term-ReadLine-Perl
%%SITE_PERL%%/Term/ReadLine/Perl.pm
%%SITE_PERL%%/Term/ReadLine/readline.pm

So I think it is solved and could be closed.
Comment 3 Walter Schwarzenfeld 2018-02-25 22:27:41 UTC 
No, is not!
Comment 4 freebsd 2022-03-10 07:10:03 UTC 
Do not care anymore due to lack of response.