Bug 58636 - Broken PERL_LEVEL check
Summary: Broken PERL_LEVEL check
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: Yen-Ming Lee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-28 15:50 UTC by Jeremy Chadwick
Modified: 2003-10-28 16:30 UTC (History)
0 users

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 Jeremy Chadwick 2003-10-28 15:50:19 UTC 
	The PERL_LEVEL check is broken and incorrect; the value is not formatted
	in such a way (see ports/Mk/bsd.port.mk).  This causes duplicate copies
	of the same module to end up being installed on the host.  Test::Simple
	and Test::Harness (the same versions none the less!) already come with
	perl-5.8.  I'm not sure if they come with perl 5.6.

Fix: 

Change the PERL_LEVEL check from 580000 to 500800.

	Also, is there any chance we could get one of the ports maintainers to
	go through all of the ports recursively to look for broken PERL_LEVEL
	checks?  My guess is that there are more than a few ports exhibiting
	this behaviour, and we might as well squash them all in one blow.
How-To-Repeat: 	Install razor-agents on a box with perl-5.8 installed.  You will have
	two copies of Test::Simple and Test::Harness floating around.
Comment 1 Erwin Lansing freebsd_committer freebsd_triage 2003-10-28 15:52:29 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->leeym

Over to maintainer
Comment 2 Yen-Ming Lee freebsd_committer freebsd_triage 2003-10-28 15:59:14 UTC 
State Changed
From-To: open->closed

Committed, thanks.
Comment 3 Oliver Eikemeier 2003-10-28 16:24:42 UTC 
Jeremy Chadwick wrote:

> 	The PERL_LEVEL check is broken and incorrect; the value is not formatted
> 	in such a way (see ports/Mk/bsd.port.mk). [...]
> 
> 	Also, is there any chance we could get one of the ports maintainers to
> 	go through all of the ports recursively to look for broken PERL_LEVEL
> 	checks?  My guess is that there are more than a few ports exhibiting
> 	this behaviour, and we might as well squash them all in one blow.

This seems to be the only case:

# grep -r PERL_LEVEL /usr/ports | grep -v '500[68]0[01]'

You don't have to be a port maintainer, though ;-)

Regards
    Oliver