| 1 |
On 11/24/2015 09:24 AM, Joakim Tjernlund wrote: |
| 2 |
> I have created my own set, @cusfpv3, and now I want to |
| 3 |
> include this set in @world using my custom profile. |
| 4 |
> How can I do that? |
| 5 |
> |
| 6 |
> I can add it in overlay/sets.conf: |
| 7 |
> [CUSFPv3 sets] |
| 8 |
> class = portage.sets.files.StaticFileSet |
| 9 |
> multiset = true |
| 10 |
> directory = %(PORTAGE_CONFIGROOT)s${repository:tmv3-target-overlay}/sets/ |
| 11 |
> |
| 12 |
> [world] |
| 13 |
> class = portage.sets.base.DummyPackageSet |
| 14 |
> packages = @cusfpv3 @profile @selected @system |
| 15 |
> |
| 16 |
> But then this set becomes active as soon as one add the overlay to |
| 17 |
> a machine and I do not want that. |
| 18 |
> |
| 19 |
> Jocke |
| 20 |
> |
| 21 |
|
| 22 |
We could extend the @profile set to support nested sets. Would you like |
| 23 |
to file a feature request bug? For example, I requested support for the |
| 24 |
@profile set in this bug: |
| 25 |
|
| 26 |
https://bugs.gentoo.org/show_bug.cgi?id=532224 |
| 27 |
-- |
| 28 |
Thanks, |
| 29 |
Zac |
Archives