Mantis - pkg_get
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2287 regular use feature always 2007-07-14 07:22 2009-02-27 02:19
Reporter: obx Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: closed Product Version:  
Product Build: Resolution: not fixable  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0002287: naming inconsistency, stop guessing package names (eg: OpenSSL)
Description: It would be a BIG useability improvement if pkg-add accepted program name, package name, and name from \'pkg-get -a\' (typically, binary name) without distinction.

Incidentally, couldn\'t we enforce better consistency?

for example, given:
-----------------------
application CSWossl openssl - The Open Source toolkit for SSL and TLS

all these 3 would work:
-----------------------
pkg-add -i openssl
pkg-add -i ossl
pkg-add -i CSWossl
Steps To Reproduce:
Additional Information: Implementation of automagic pkg name resolution is trivial:
- first try as specified
- else, if name matches a name from `pkg-get -a | awk \'{print $1}\'` , use corresponding package
- else, if package given as CSWxyzt, strip leading 3 chars \'CSW\' and re-try just \'xyzt\'

When matching names, try case INsensitive matches.

If more than one name matches:
- in interactive, ask which one
- with -f, exit with both/all potential matches printed in pkginfo format

Thank you!
Relationships
related to 0003453closed phil have pkg_get accept CSWxxx names, as well as software names, for operations. 
Attached Files:
Issue History
Date Modified Username Field Change
2008-11-13 20:49 philadmin Note Added: 0005388
2008-11-14 13:38 dam Note Added: 0005399
2009-02-27 02:17 phil Relationship added related to 0003453
2009-02-27 02:19 phil Note Added: 0005575
2009-02-27 02:19 phil Status new => closed
2009-02-27 02:19 phil Resolution open => not fixable

Notes
(0005388)
philadmin   
2008-11-13 20:49   
I dont think it is reasonable to "guess" at having "ossl" work,in your example. but I do think it is reasonable to have it try for the PKGxxx name.
I intend to add that functionality in some future release.
possibly only the 4.0 version. current beta is on http://mirrors.opencsw.org/testing [^] I think.
(0005399)
dam   
2008-11-14 13:38   
Actually http://mirror.opencsw.org/testing [^]
(0005575)
phil   
2009-02-27 02:19   
Wow. old bug.

And ambigously worded.
I cant change the "summary" line fairly, so I'm going to close this one, and open a more focused one.
I've already linked the two together i think: to bugid 3453


Some comments on close:


first of all, MY program is "pkg-get", not pkgadd. I cant change the behaviour of pkgadd; that's sun's! :-)

secondly; the pkg-get handling of "program name" is quite consistent.
Output of "pkg-get -a" (and pkg-get -c) shows that name, and that is exactly what pkg-get accepts.

Now, on the other hand, the pkgadd internal database "name".. the CSWxxxx, has some restrictions on it.
It WOULD be nice if pkg-get accepted that name as well. and I intend to make it do so at some point, but it's low priority.

I'm replacing this with a more cleanly named bug, to help me remember more easily in the future.