[bug-notifications] [pkgutil 0003894]: pkgutil 1.7: -L option only works with the package name, not the software name
Mantis Bug Tracker
noreply at opencsw.org
Thu Sep 17 14:26:24 CEST 2009
A NOTE has been added to this issue.
======================================================================
http://www.opencsw.org/mantis/view.php?id=3894
======================================================================
Reported By: skayser
Assigned To: bonivart
======================================================================
Project: pkgutil
Issue ID: 3894
Category: regular use
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2009-09-14 11:16 CEST
Last Modified: 2009-09-17 14:26 CEST
======================================================================
Summary: pkgutil 1.7: -L option only works with the package
name, not the software name
Description:
Most other command options work with both (pgk and sw name), the new -L
option only seems to work with the sw name. Can we get it to recognize the
sw name too?
Example:
# pkgutil -L dhcp
# pkgutil -L CSWdhcp | head
/etc/init.d/cswdhcp
/etc/opt/csw/dhcpd.conf.CSW
/etc/rc1.d/K73cswdhcp
/etc/rc2.d/S73cswdhcp
/opt/csw/bin/omshell
/opt/csw/include/dhcpctl.h
/opt/csw/include/isc-dhcp
/opt/csw/include/isc-dhcp/boolean.h
/opt/csw/include/isc-dhcp/dst.h
======================================================================
----------------------------------------------------------------------
(0006714) bonivart (manager) - 2009-09-17 14:26
http://www.opencsw.org/mantis/view.php?id=3894#c6714
----------------------------------------------------------------------
I need to make a catalog lookup to find the package name since that's
what's in the contents file. Otherwise I would need to extract the
NAME-field from every package on the system with pkgparam or something and
that would take minutes.
Pkgutil always uses package names internally, catalog names are just for
convenience. In most cases it doesn't matter but with testing I suppose it
does in a bad way.
If you have ideas I'm all ears.
The extra blank line is there to separate between files from multiple
packages you may specify on the command line. That it's displayed when only
one package is used is just me being lazy. It annoys me too and I will fix
it...someday. :-)
More information about the bug-notifications
mailing list