On Mon, 02 Mar 2009 15:26:33 +0900, Bret Busby wrote: > Synaptic installs then loses packages; it downloads and installs a package > and its dependencies, and then, when queried, it shows the package and its > dependancies to be installed, but it does not add the packages to the > menu, and, in the Properties dialogue box in Synaptic, it shows the > application category, where I assume that the application should be added > to the Applications menu hierarchy; under the label of Section, on the > Common tab, but it does not show anything like a path to the package > executable file, so, basically, the package gets installed and then lost, > so it cannot be used.
Well, it's not really "lost". You would be able to run the installed package by entering the appropriate command for the package at the command line of a terminal. If the package maintainer chooses to not have package configuration automagically add it to a menu that doesn't mean it is lost or won't work. The system administrator (who installs the package as root) can decide which and who's menu the package shows up in and that is the behaviour I prefer, perhaps others also do. By the way, since you use Synaptic, if you check the properties of the package from the Synaptic menu and look at the "Installed Files" tab it will show you where all of the files from the package have been installed. That will give you the location of the executable binary for the package. In addition, it shows the location for any documentation installed, which might be useful to you sometime. All of this can also be done from the command line but you probably want to use the GUI that you are already using. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
