Bug 64963 - Perl 5.8: make package deletes installed perl binary
Summary: Perl 5.8: make package deletes installed perl binary
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Anton Berezin
Depends on:
Reported: 2004-03-31 03:10 UTC by Tony Maher
Modified: 2006-01-05 00:56 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Tony Maher 2004-03-31 03:10:12 UTC
Perl 5.8.0_6 is installed. Tried to make package with latest perl (5.8.2) which failed but /usr/local/bin/perl was deleted.


Rev 1.65 of the Makefile introduced a pre-install target that deletes
${PREFIX}/bin/perl (and PERL_VER).

Surely this is against POLA.
I do not expect make install (or package) to delete anything in the installed system.
The CVS log indicate that this was done to overcome weird symlinking possibly from portupgrade.  *IF* this is the case then fixing portupgrade would be preferable.

Should not the perl ports install the actual perl binary as perl${version} and just have perl a symlink to the version?
Rather than the current:
-rwxr-xr-x  1 root  wheel  811876 Apr 29  2003 perl*
lrwxr-xr-x 1 root wheel 19 Mar 31 10:20 perl5@ -> /usr/local/bin/perl
lrwxrwxrwx 1 root wheel 19 Mar 31 10:20 perl5.8.0@ -> /usr/local/bin/perl
How-To-Repeat: Perl 5.8.0_6 installed.
cd /usr/ports/lang/perl5.8
grep PERL_VER= Makefile
PERL_VER=       5.8.2
make package
Comment 1 Mark Linimon freebsd_committer 2004-03-31 13:54:01 UTC
Responsible Changed
From-To: freebsd-ports-bugs->tobez

Over to maintainer.
Comment 2 Edwin Groothuis freebsd_committer 2006-01-05 00:49:10 UTC
State Changed
From-To: open->closed

Despite that I agree with your reasoning, I also see that this shows 
the power of the ports framework. 

For any other port which doesn't conflict with other ports (unlike 
what lang/perl5.8 and lang/perl5, x11-wm/fvwm2 and x11-wm/fvwm2-devel 
etc do) I would say "yes, deleting there is wrong". But for this 
situation where multiple ports install the same file, this is how 
it can be resolved.