Feature changed by: Gerald Pfeifer
Feature #305491, revision 28
Title: package names should also be binary names
openSUSE-11.2: Evaluation
Priority
Requester: Desirable
SLED-11-SP1
SLES-11-SP1
Requested by: Juergen Weigert (jnweiger)
+ Interested: Federico Lucifredi (flucifredi)
Interested: Kai Dupke (kdupke)
Interested: Marcus Kraft (marcuskraft)
Interested: Stefan Behlert (sbehlert)
Partner organization: openSUSE.org
Description:
Many packages providing command line applications do so with commands
named different than the package
Random examples: install cpuset but call cset; install lvm2 but call
lvm; install MPlayer but call mplayer, install MozillaFirefox but call
firefox, install NetworkManager-kde but call knetworkmanager; install
OpenOffice_org but call soffice/ooffice/oowriter
I suggest to create one shell script per package, that is named exactly
as the package is named, which tells the user how to use the package
(unless a binary with that name already exists). This script could
point to existing binaries, print documentation, or simply be a symlink
to an existing binary if there is one prominent user callable entry
point, whatever makes sense.
Discussion:
#2: Thorsten Kukuk (kukuk) (2008-11-25 05:58:17)
Veto. We decided to name RPMs after the name of the upstream package,
especially to be in sync with other distributions and don't confuse
ISVs and customers completlty.
I don't see any benefit for customers, but only disadvantages for
everybody.
Between, business case for this very cost-intensiv feature is missing.
#3: Thorsten Kukuk (kukuk) (2008-11-25 05:59:18)
How would you call "pwdutils"? "useradd"? "userdel"? "passwd"? Split
them in 100 little RPMs?
#10: Thomas Schmidt (digitaltomm) (2008-11-26 12:00:29)
This could be added to the command-not-found tool
(http://en.opensuse.org/Scout , don't know whether this is available on
SLES). When a command is not found, but scout sees a RPM with exactly
this name installed it could display a list of the included binaries.
This way no packages would need to be changed, it's only an enhancement
to command-not-found.
#11: Kai Dupke (kdupke) (2008-11-26 12:43:29) (reply to #10)
scout is part of the SLES media. Looks like an answer on how to handle
this. Not sure if we install this by default.
#14: Pavol Rusnak (prusnak) (2009-01-09 15:56:02) (reply to #11)
I and mvyskocil are creators and maintainers of scout. All you need to
do is to issue (after installing scout of course):
$ scout bin firefox
repository | binary | path | package
--------------------+---------+----------+----------------
zypp (11.1-oss) | firefox | /usr/bin | MozillaFirefox
What else needs to be done?
#16: Pavol Rusnak (prusnak) (2009-01-09 15:57:33) (reply to #14)
I forgot to note that scout is automatically installed in base system
in openSUSE 11.1.
#17: Juergen Weigert (jnweiger) (2009-01-09 16:43:41) (reply to #11)
Hey, thanks for creating scout. This is very helpful.
Currently, I can map from binary to package, by using 'scout bin'
This feature is about the reverse, mapping from package to binary. Can
this be added to scout?
Integration with /usr/bin/command-not-found would be very helpful then.
E.g.
bash$ MPlayer
Package MPlayer includes the following binaries:
repository | binary | path | package
---------------------------+---------+----------+---------
zypp (Packman Repository) | mplayer | /usr/bin | MPlayer
How do we educate our users about the existance of scout?
#19: Pavol Rusnak (prusnak) (2009-01-09 17:30:10) (reply to #17)
After discussion with Michal, we'll add -p parameter to each module,
which will indicate that package name is provided, not search_term. All
modules will benefit from that change, not only "bin", so user could
also list all java classes from java package and so on.
I'm not quite sure about the command-not-found integration. There are
some people who don't like the speed of handler and another extra
search will add another fractions of seconds. If user wants that
feature, he'll just types:
$ scout bin -p MPlayer
#15: Michael Loeffler (sprudel24) (2009-01-09 15:58:57) (reply to #10)
The Scout way sounds like a good solution.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=305491