pkg/27245: perl dependencies should be more strict

[reed%reedmedia.net@localhost]

>Number:         27245
>Category:       pkg
>Synopsis:       perl dependencies should be more strict
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 13 02:50:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6.2_STABLE
>Organization:
http://bsd.reedmedia.net/
>Environment:
        
        
System: NetBSD rainier.reedmedia.net 1.6.2_STABLE NetBSD 1.6.2_STABLE 
(MYKERNEL) #1: Tue Jun 1 12:16:43 PDT 2004 
reed%rainier.reedmedia.net@localhost:/usr/src/sys/arch/i386/compile/MYKERNEL 
i386
Architecture: i386
Machine: i386
>Description:
When perl-5.8.3 is installed, packages that depend on perl usually have
open-ended dependency like:
perl>=5.0 (or {perl>=5.0,perl-thread>=5.0}).

So then these packages that were built using perl-5.8 may end up
being used with perl-5.6 and fail.

Also there doesn't appear to be a way to choose the perl to install
if not already installed and will default to perl-5.6. Maybe it would
be good to  have a PERL_VERSION_DEFAULT that can be defined like
PYTHON_VERSION_DEFAULT.
>How-To-Repeat:
Install perl-5.8 instead of perl-5.6. Build some packages that
depend on perl.

Attempt to reuse those packages on a 5.6 system.

Or visa-versa.
>Fix:
Add a PERL_VERSION_DEFAULT variable so a default perl can be chosen
ahead of time.

Fix mk/bsd.pkg.mk so it will have a more specific DEPENDS for the
perl used, like perl-5.6.*.
>Release-Note:
>Audit-Trail:
>Unformatted: