What about piping the output of emerge through 'tee' into a file. You
can then grep that file for the package names you are interested in, and
they will clearly be highlighted. True, you will need to look at the
portage output directly to decide whether or not to proceed, and then
separately at the grep of the same text to see if you need to take other
actions.
On 7/8/23 16:20, Dale wrote:
Neil Bothwick wrote:
On Sat, 8 Jul 2023 14:14:46 -0500, Dale wrote:
Thing is, some of the packages are dependencies of other packages.
Excluding them will likely trigger other problems, such as packages not
being able to upgrade due to others being excluded. Plus, I'd have to
run it twice and do two separate upgrades. Usually, I start the upgrade
in a chroot, take a nap and it is done when I wake up. I'd have to
interrupt my nap for the second set if it is split up.
Having it highlight the packages so I can see them easier was a thought,
just not a good one. :/
But what would you do with the information? If you're just going to see
that there are slow packages there and then carry, what's the point. I
suppose you know you can have a longer nap :)
You could try piping emerge's output through sed to add colour codes
around the packages you want to highlight. How exactly you do this is
left as an exercise for the reader :P
When I see certain packages, I know to close some of my Firefox profiles
if they require a lot of memory. For some, I know I need to restart
that program/service. For some, such as my video drivers, I know to
reload the modules after I logout. What I do with the info depends on
which package it is. I just make a mental note that certain things
needs to be done and I know to do them either before I start the upgrade
or after it is done.
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. :/
Dale
:-) :-)
