On 08/07/2023 21:20, Dale wrote:
Just as a example, my overnight upgrade included nvidia drivers. I
didn't see it so when I logged out, no X. I usually see it but missed
it this time. Having a way to easily set the colors would be easier but
having to repeat things, create files to scan, use tools I'm not
familiar with and such, that isn't easy. I wanted to be able to see it
in the initial list, make a note of what packages I need to do things
for and then hit yes to continue. Basically, I was hoping emerge had a
way to do this that isn't known to me. After all, the thing all but
washes dishes already. ROFL
Maybe one day others will like this idea and one of them is willing to
add some code to emerge to do it. Until then, I guess I'll just miss
one on occasion and have to scratch my head a couple times.
Thanks to all. Interesting ideas but generally over my head. :/
Something I saw elsewhere - why don't you put all of these programs into
a list like @system or @world. You can exclude these programs from an
"emerge @world".
I don't know whether these programs will be emerged as dependencies of
an "emerge @world", but if you want to know if they will be emerged, an
"emerge @... --pretend" will tell you.
So firstly, you know whether any of these programs are going to be
emerged. Secondly, you can emerge all the hogs in one go. And thirdly,
you you can emerge @world before or after.
So, I guess, if you don't exclude these hogs from @world then you can
just find out if they are going to be emerged (and emerge them first if
you want), or if you do exclude them from @world, you can emerge them
(to some extent at least) on your own timescale.
Cheers,
Wol
