1 |
On 20/11/2016 02:43, Harry Putnam wrote: |
2 |
> |
3 |
> [...] |
4 |
> |
5 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
6 |
> |
7 |
>> You can create a set containing a list of packages. I do this for |
8 |
>> dependencies of packages that are not from portage, so they don't get |
9 |
>> depcleaned and don't end up in @world. Something like |
10 |
> |
11 |
> [...] |
12 |
> Thanks for the nifty examples... ... missing entirely in the pile of |
13 |
> documenation at /usr/share/doc/portage-2.3.2/html/index.html |
14 |
> (if you have USE=doc set) |
15 |
> |
16 |
>> % cat /etc/portage/sets.conf |
17 |
>> [kernels] |
18 |
>> class = portage.sets.dbapi.OwnerSet |
19 |
>> world-candidate = False |
20 |
>> files = /usr/src |
21 |
>> |
22 |
>> then emerge -n @kernels |
23 |
> |
24 |
> This one kind of sails right over my head... not seeing what is |
25 |
> supposed to happen. |
26 |
> |
27 |
> [...] |
28 |
> |
29 |
> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
30 |
> |
31 |
> [...] |
32 |
> |
33 |
>> Think of it as sort of like a magic meta-package that you define - a set |
34 |
>> gets merged as a unit and where you unmerge it, the sets is out of world |
35 |
>> and depclean will take care of removing the members. |
36 |
>> |
37 |
>> Simple as that. I'm not aware of anything in FEATURES related to sets, |
38 |
>> you just use them out the box. |
39 |
> |
40 |
> Gack, I was following along OK until the part about `out of the box' |
41 |
> |
42 |
> Do you mean those toxic looking definitions or other stuff in the docs |
43 |
> at /usr/share/doc/portage-2.3.2/html/index.html? ... |
44 |
> |
45 |
> |
46 |
|
47 |
|
48 |
No, I mean: |
49 |
|
50 |
install portage |
51 |
vi /etc/portage/sets/mystuff |
52 |
emerge @mystuff |
53 |
|
54 |
|
55 |
-- |
56 |
Alan McKinnon |
57 |
alan.mckinnon@×××××.com |