| View previous topic :: View next topic |
| Author |
Message |
chrisl456
n00b
Joined: 12 Jan 2004
Posts: 18
|
 Posted: Wed Apr 21, 2004 6:29 am Post subject: How to find what ebuild provides a file? |
 |
|
Hello,
I'm still fairly new to Gentoo (but not linux), so I'm likely missing something stupid. I'm trying to figure out what ebuild provides the file "/usr/bin/ksysguardd", so I can install it. On a Redhat/Mandrake box, I'd just go to rpmfind.net and do a search for the name of the file I need & it would tell me which RPM's provide that file. How can I get similar functionality from Gentoo? I've tried "qpkg -U -f /usr/bin/ksysguardd" and also searching on packages.gentoo.org.
Thanks for helping out a noob,
Chris |
|
| Back to top |
|
 |
fcgreg
Apprentice
Joined: 17 May 2003
Posts: 264
Location: California, USA
|
| Posted: Wed Apr 21, 2004 7:27 am Post subject: Try a different command |
|
|
FYI: The command you are using (qpkg) is being phased out soon. Also, it doesn't do quite what you want.
The better command for this is equery. The following command syntax should work:
| Code: | | equery belongs /usr/bin/ksysguardd |
However, this still won't help you in your particular case. Portage isn't like the RPM system, where everything is precomiled and all information stored ahead of time. Since Portage compiles from sources, it doesn't know about an executable before it has been installed. To know such a thing it would have to store information about every file for every package in the entire Portage tree -- installed or not. This would be a humongous task, and would essentially require all of our systems to become an rpmfind-style repository!
However, Portage can tell information about all the files already installed on the system. In fact, I think it retains most/all of this information even after a package has been uninstalled as well, but I don't know if this is still true, as this would have dubious benefit for most.
In any case, this isn't going to help your situation. A simple Google search may be the best thing for you.
I hope that helps!
_________________
Greg T. |
|
| Back to top |
|
|
chrisl456
n00b
Joined: 12 Jan 2004
Posts: 18
|
| Posted: Mon Apr 26, 2004 11:16 pm Post subject: |
|
|
Thanks for the info!
Actually, getting something like you described to work sounds like an interesting programming project. Maybe by watching what files are installed for an ebuild under several "ideal" configurations... or, for that matter, make all the ebuild maintainer people supply the information. But maybe they won't like that idea. 
Unfortunately, I don't have the time to dive into something like this.
Chris |
|
| Back to top |
|
|
robmoss
Retired Dev
Joined: 27 May 2003
Posts: 2634
Location: Jesus College, Oxford
|
| Posted: Mon Apr 26, 2004 11:18 pm Post subject: |
|
|
Yeah, I tend to use Google myself - it's the easiest way. In theory it would be possible to have a (perhaps online) database, but it wouldn't be very good I don't think. The very fact that you compile everything from source means that the names of the binaries are hard to pick out of the tarballs, because there's no standard way of doing that.
_________________
Reality is for those who can't face Science Fiction.
emerge -U will kill your Gentoo
ecatmur, Lord of Portage Bash Scripts |
|
| Back to top |
|
|
Earthwings
Bodhisattva
Joined: 14 Apr 2003
Posts: 7753
Location: Germany
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Duplicate Threads
