0003917: bldcat/chkcat rely on /opt/csw/bin/perl, but CSWpkgutil doesn't have dependency on CSWperl

OpenCSW Bug Tracker

Project:

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0003917

[pkg_get] packaging

minor

always

2009-09-23 17:02

2009-09-28 13:44

Reporter

skayser

View Status

public

Assigned To

bonivart

Priority

normal

Resolution

fixed

Status

closed

Summary

0003917: bldcat/chkcat rely on /opt/csw/bin/perl, but CSWpkgutil doesn't have dependency on CSWperl

Description

I understand that CSWpkgutil should not depend on CSWperl, but bldcat/chkcat are both hardcoded to use /opt/csw/bin/perl. Just wanted to build a catalog on a system that only has /usr/bin/perl and catalog creation failed.

$ /opt/csw/bin/bldcat
bash: /opt/csw/bin/bldcat: bad interpreter: No such file or directory

$ head -1 /opt/csw/bin/bldcat
#!/opt/csw/bin/perl -w

$ head -1 /opt/csw/bin/chkcat
#!/opt/csw/bin/perl -w

$ pkginfo -l CSWperl
ERROR: information for "CSWperl" was not found

Unfortunately, they don't work with the stock perl due to missing perl modules.

$ /usr/bin/perl /opt/csw/bin/bldcat .
Can't locate Digest/MD5.pm in @INC (@INC contains: /usr/perl5/5.6.1/lib/sun4-solaris-64int /usr/perl5/5.6.1/lib /usr/perl5/site_perl/5.6.1/sun4-solaris-64int /usr/perl5/site_perl/5.6.1 /usr/perl5/site_perl /usr/perl5/vendor_perl/5.6.1/sun4-solaris-64int /usr/perl5/vendor_perl/5.6.1 /usr/perl5/vendor_perl .) at /opt/csw/bin/bldcat line 9.
BEGIN failed--compilation aborted at /opt/csw/bin/bldcat line 9.

Any chance to ship the required modules with CSWpkgutil?

Additional Information

$ pkgutil -v
1.7

Tags

No tags attached.

Attached Files

Relationships

Notes
(0006745) bonivart (developer) 2009-09-23 18:23	I want to make pkgutil as free of deps as possible, it currently has none so you can use it immediately even if on Solaris 8 with Perl 5.5.3 from 1999(?). The chkcat/bldcat utilities are different though, they use (not optional) a few modules that are not included in the core dist of old Perl but it's easy to get our new Perl when you have a working pkgutil. :-) I'm thinking about making something like CSWpkgutilplus that depends on a few things like our Perl, GPG and Curl. Installing it would "unlock" features like parallel downloads. What do you think about that? I want to keep pkgutil as simple as possible to make it bootstrappable but advanced features requires (up to date) dependencies.

(0006748) skayser (administrator) 2009-09-23 19:51	A separate package for tools that have additional dependencies sounds good to me. Don't quite know about introducing enhanced features of pkgutil via an extra package, though. Shouldn't people just need to be concerned with one pkg* package. How about some sort of auto-discovery of additional tools? If they are installed, use the features, if not, don't. Maybe add a pkgutil --pimpme switch to install those extra-deps. ;)

(0006763) bonivart (developer) 2009-09-28 13:44	I changed it so that both bldcat and chkcat uses whatever Perl is in the path (like pkgutil) and if Digest::MD5 is not available you get a message about that and a recommendation to install CSWperl. Modern Solaris will have this module in their standard Perl so it's not a strict requirement to use CSWperl any more unless you're on like Solaris 8.