| 1 |
Paul Hartman wrote: |
| 2 |
> On Thu, Jun 11, 2009 at 11:45 AM, Mike Kazantsev<mk.fraggod@×××××.com> wrote: |
| 3 |
> |
| 4 |
>>> So, my question: Is there a way to tell depclean to never remove *any* |
| 5 |
>>> version of gentoo-sources? |
| 6 |
>>> |
| 7 |
>> That's where portage-2.2 sets find another use. |
| 8 |
>> Just add following set to /usr/share/portage/config/sets.conf: |
| 9 |
>> |
| 10 |
>> [kernels] |
| 11 |
>> class = portage.sets.dbapi.OwnerSet |
| 12 |
>> world-candidate = False |
| 13 |
>> files = /usr/src |
| 14 |
>> |
| 15 |
>> And append "@kernels" line to /var/lib/portage/world_sets |
| 16 |
>> Now any installed (even with -1) kernel should be safe from ravenous |
| 17 |
>> depclean. |
| 18 |
>> |
| 19 |
> |
| 20 |
> Perfect! It does exactly what I wanted. I created sets.conf in |
| 21 |
> /etc/portage/ as Boris pointed out. |
| 22 |
> |
| 23 |
> Thank you very much for your help! |
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
What would I add to /etc/portage/sets.conf to exclude gcc from depclean? |
| 28 |
thanks |
| 29 |
-david |
| 30 |
|
| 31 |
-- |
| 32 |
Powered by Gentoo GNU/Linux |
| 33 |
http://linuxcrazy.com |
Archives