1 |
On 19/11/2016 18:04, Harry Putnam wrote: |
2 |
> Can anyone post, in laymans, terms how to use sets.conf. Or thru |
3 |
> FEATURES if thats how its done, I've read the posrtage manpage that |
4 |
> covers it and this URL: |
5 |
> |
6 |
> https://dev.gentoo.org/~zmedico/portage/doc/ch02s02.html#config-set-syntax-single |
7 |
> |
8 |
> Finally reinstalled portage with USE="doc" to get the html set |
9 |
> referred to in portage manual as the definitive place to learn about sets |
10 |
> |
11 |
> But honestly I left those without a stinking clue how to actually use sets |
12 |
> for things like avoiding specific packages being depcleaned. I mean |
13 |
> besides putting them in `world' |
14 |
> |
15 |
> There seems to be a durth of what actually to put into make.conf under |
16 |
> FEATURES or whatever... |
17 |
> |
18 |
> I want to protect certain pkgs from depclean.... how can I put a small |
19 |
> list under `sets' management in make.conf or sets.conf or .... |
20 |
> |
21 |
> |
22 |
|
23 |
|
24 |
there are some rather old docs floating around that describe amazing |
25 |
things you can do with sets, but I think those were flights of fantasy |
26 |
and never got implemented. The main feature of sets is simply this: |
27 |
|
28 |
list a bunch of packages in a text file in the right place, and the now |
29 |
have a set named the same as the file name. You can emerge this set |
30 |
using an "@" like: |
31 |
|
32 |
emerge @harry_set |
33 |
|
34 |
Effectively, the packages in @harry_set are effectively in world, |
35 |
without actually being in the world file. The set instead is in |
36 |
/var/lib/portage/world_sets. |
37 |
|
38 |
Think of it as sort of like a magic meta-package that you define - a set |
39 |
gets merged as a unit and where you unmerge it, the sets is out of world |
40 |
and depclean will take care of removing the members. |
41 |
|
42 |
Simple as that. I'm not aware of anything in FEATURES related to sets, |
43 |
you just use them out the box. |
44 |
|
45 |
|
46 |
-- |
47 |
Alan McKinnon |
48 |
alan.mckinnon@×××××.com |