1 |
On Fri, 12 Jun 2009 15:11:07 -0400 |
2 |
David <david@×××××××××.com> wrote: |
3 |
|
4 |
> What would I add to /etc/portage/sets.conf to exclude gcc from depclean? |
5 |
> thanks |
6 |
|
7 |
I'd add these to sets: |
8 |
|
9 |
[gcc-preserve] |
10 |
class = portage.sets.shell.CommandOutputSet |
11 |
command = /usr/local/sbin/gcc-list |
12 |
|
13 |
This to /usr/local/sbin/gcc-list: |
14 |
|
15 |
#!/bin/sh |
16 |
for PKG in `ls -1 /var/db/pkg/sys-devel | grep -E '^gcc-[[:digit:].]+(-r.)?$'` |
17 |
do echo '=sys-devel/'${i} |
18 |
done |
19 |
|
20 |
And '@gcc-preserve' to /var/lib/portage/world_sets |
21 |
|
22 |
|
23 |
Alternatively, you can define set as files in /usr/libexec/gcc: |
24 |
|
25 |
[gcc-preserve] |
26 |
class = portage.sets.dbapi.OwnerSet |
27 |
world-candidate = False |
28 |
files = /usr/libexec/gcc |
29 |
|
30 |
Looks simplier, but somewhat dirty and probably a bit slower. |
31 |
|
32 |
-- |
33 |
Mike Kazantsev // fraggod.net |