| 1 |
Dr Rainer Woitok wrote: |
| 2 |
> Wol, |
| 3 |
> |
| 4 |
> On Sunday, 2022-02-20 14:56:20 +0000, you wrote: |
| 5 |
> |
| 6 |
>> ... |
| 7 |
>> But --deep - that's to do |
| 8 |
>> with a dependency changing USE flags, and it will block a depclean if |
| 9 |
>> you don't do it. |
| 10 |
> Thanks for the reminder! This is in fact mentioned in every output from |
| 11 |
> "emerge --depclean" and thus develops a high probability of being ignor- |
| 12 |
> ed ... :-) |
| 13 |
> |
| 14 |
> So my script will keep "--deep" when "--update" is specified. But what |
| 15 |
> about "--changed-deps"? Can nobody on this list explain what it really |
| 16 |
> is or isn't good for, or when to use or not to use it? |
| 17 |
> |
| 18 |
> Sincerely, |
| 19 |
> Rainer |
| 20 |
> |
| 21 |
> |
| 22 |
|
| 23 |
|
| 24 |
I read what the man page says. For me, it isn't very clear. I'm sure |
| 25 |
you read it and came to the same conclusion. This is my thoughts, and I |
| 26 |
am certainly capable of being very wrong here. Lets say package A |
| 27 |
depends on package B. Package B changes and could affect package A. |
| 28 |
The --changed-deps should trigger a rebuild/reinstall of package A. |
| 29 |
Sometimes package A can link to parts of package B and changing package |
| 30 |
A can affect that if there is a sizable change. It may even make |
| 31 |
package A not work or crash. |
| 32 |
|
| 33 |
That's my thinking. Like I said, I could be wrong or have it |
| 34 |
backwards. The man page just isn't worded in a way that makes sense to |
| 35 |
me. Of course, I don't have a decoder for emerge either. :/ |
| 36 |
|
| 37 |
Anyone have a better explanation?? |
| 38 |
|
| 39 |
Dale |
| 40 |
|
| 41 |
:-) :-) |
| 42 |
|
| 43 |
P. S. I tried tkman to read man pages. It pukes a error and doesn't |
| 44 |
work. Something changed in the man command and I don't like it. I'm |
| 45 |
looking for a GUI man page tool. Any ideas? Off list if needed. I |
| 46 |
noticed this when trying to read the emerge man page. |
Archives