| 1 |
On Thu, 19 Feb 2015 22:56:20 +0000 (UTC), James wrote: |
| 2 |
|
| 3 |
> Neil Bothwick <neil <at> digimed.co.uk> writes: |
| 4 |
|
| 5 |
> > > So for a given eclass, how to I find the list of all ebuilds |
| 6 |
> > Well, brute force works |
| 7 |
> |
| 8 |
> > grep -Er 'inherit.*systemd' /var/portage |
| 9 |
> |
| 10 |
> '/usr/portage/' works for me, when bruting. |
| 11 |
|
| 12 |
Yes, I'd forgot to adjust for my moving the portage tree to a more |
| 13 |
logical location :) |
| 14 |
|
| 15 |
> > That shows every ebuild, you may want to reduce it to a list of |
| 16 |
> > packages |
| 17 |
> |
| 18 |
> > for i in $(grep -Erl 'inherit.*systemd' /var/portage) |
| 19 |
> > do |
| 20 |
> > dirname $i |
| 21 |
> > done | sort -u |
| 22 |
> |
| 23 |
> |
| 24 |
> Yea, sure, cool. (THANKS). However, I was looking for (wink wink nudge |
| 25 |
> nudge) something sexy, using VDB (/var/db/pkg/) |
| 26 |
|
| 27 |
That only shows installed packages. If you want something a little more |
| 28 |
portagey, you could use qgrep. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Neil Bothwick |
| 33 |
|
| 34 |
Disinformation is not as good as datinformation. |
Archives