Subject: i386 solaris pkgsrc, already have perl5
To: None <tech-pkg@NetBSD.org>
From: Hal Snyder <hal@vailsys.com>
List: tech-pkg
Date: 10/07/2003 18:02:27
Getting feet wet with pkgsrc on i386 Solaris 2.8, I wonder about the
following situation:

we already have perl5 installed outside pkgsrc:

>type perl 
perl is /usr/local/bin/perl
>perl -version

This is perl, v5.6.1 built for i86pc-solaris
...

I would like to use that installation, if possible.
I have tried setting /etc/mk.conf thus:

PERL5=/usr/local/bin/perl
PERL5_SITELIB=/usr/local/lib/perl5/site_perl/5.6.1
PERL5_ARCHLIB=/usr/local/lib/perl5/5.6.1/i86pc-solaris
PERL5_SITEARCH=/usr/local/lib/perl5/site_perl/5.6.1/i86pc-solaris

but still get for example the following:

/usr/pkgsrc/security/openssl#bmake extract
===> *** No /export/home/u1/usr.pkgsrc/distfiles/pkg-vulnerabilities file found,
===> *** skipping vulnerability checks. To fix, install
===> *** the pkgsrc/security/audit-packages package and run
===> *** '/usr/pkg/sbin/download-vulnerability-list'.
=> Checksum OK for openssl-0.9.6k.tar.gz.
===> Extracting for openssl-0.9.6k
===> Required package perl>=5.0: NOT found
===> Verifying reinstall for ../../lang/perl5
....

Is there something else to set to prevent the build of perl5.6.x from
pkgsrc? Or is it crazy to even try this?


Of course it would be cleaner from the pkgsrc viewpoint to use
everything from pkgsrc. But, we're evaluating use of pkgsrc on a
collection of servers which already have several packages installed
outside of pkgsrc and are in production. I doubt it's practical to
replace existing packages en masse and test the entire platform -
would rather go incrementally, using pkgsrc for new packages, and
migrate gradually to pkgsrc.

Thanks.