| 1 |
On 03/21/2018 04:30 PM, M. J. Everitt wrote: |
| 2 |
> On 21/03/18 23:26, M. J. Everitt wrote: |
| 3 |
>> n 20/03/18 04:49, Manuel Rüger wrote: |
| 4 |
>>> Hi Zac, |
| 5 |
>>> |
| 6 |
>>> alternatively could --exclude be extended to support sets? |
| 7 |
>>> So users could --exclude @world or @profile. |
| 8 |
>>> |
| 9 |
>>> Cheers, |
| 10 |
>>> Manuel |
| 11 |
>>> |
| 12 |
>> The idea is sound enough, but I fear the syntax would be too confusing. |
| 13 |
>> |
| 14 |
>> Reading a potential command-line as "emerge <exclude world> <but add to |
| 15 |
>> world-file unless --no-replace specified> <My Package> puts my head into |
| 16 |
>> a spin! I can see it might be clearer for an unmerge perhaps .. |
| 17 |
>> |
| 18 |
>> Unless I'm missing something fundamental ... |
| 19 |
>> |
| 20 |
> On a related note, it would be quite handy to enumerate an |
| 21 |
> "exclude-from" option like rsync/tar(?) to specify a file with the |
| 22 |
> --exclude options in. There could be some way to append @world to this |
| 23 |
> option, perhaps? |
| 24 |
|
| 25 |
All that --ignore-world does it remove the implicit @world root the |
| 26 |
dependency graph, so --complete-graph options no longer pull @world and |
| 27 |
its deep dependencies into the dependency graph. It's still possible to |
| 28 |
use @world together with --ignore-world, but in this case --ignore-world |
| 29 |
has no effect because @world has been pulled in explicitly (and pulling |
| 30 |
@world in implicitly would be redundant in this case). |
| 31 |
-- |
| 32 |
Thanks, |
| 33 |
Zac |
Archives