Neil Bothwick wrote: > On Sat, 8 Jul 2023 15:44:47 -0500, Dale wrote: > >>> I have reused the configuration file >>> "/etc/portage/package.env/no_tmpfs.conf"[1], which already contains a >>> list of packages, which need hours to compile. >>> >>> -Ramon >>> >>> [1] >>> https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs#Per-package_choices_at_compile_time >>> >> >> I need more than just packages that take a while to compile. I need a >> list of packages that require large amounts of memory, needs restarting >> after upgrade is done and other things. I already use notmpfs on a few >> packages. That works fine. Things is, I need to know about other >> packages for other reasons as well. Upgrading nvidia is one. It uses >> little memory to upgrade but it does require the modules to be >> reloaded. > You can do a lot with package.env, including sending notifications > to remind you to do this. I also run app-admin/needrestart after each > emerge to list any services that need restarting. > >
I just wanted to be able to see them better in the output of emerge. Anything else just creates more work and consumes more time than it saves. Once I scan the list, I can hit yes and let it start. If I see Firefox, LOo or others, I close Firefox profiles, sometimes Seamonkey, to free up memory. If I see packages that are services, I know I need to restart them, even if checkrestart doesn't show it. If I see mplayer, I know that if Smplayer moves to a new video in the playlist, it will likely fail to start. Some I just know I can take a nice loooong nap. What I do just depends on the package. I just need it to be easier to see in the list. Nothing fancy, just easier to see. I use checkrestart still. I tried needrestart but it does more than I need. I found checkrestart in a overlay and I just stuck with it. Heck, I still use the rc command, even tho it gripes each time I use it. lol Dale :-) :-)
