aurutils VS kernel-modules-hook

Currently I use aurutils, so that created packages are stored in an extra repository on the respective machine and can be installed through it.

I currently use aurutils.

If I am not mistaken officially maintained packages follow the same initial process as AUR packages. You can read the wiki on Creating packages. But official packages are tested (there is a testing repository with the newest packages) where as the AUR package expects users to do the build and testing themselves, at their own risk in other words. With the helpers like glorious aurutils the process of keeping up-to-date dozens of packages (if you happen to be in a such a use case) with many dependencies is quite easy.

You could use https://github.com/AladW/aurutils to create your own pacman repository on this USB drive. On your powerful PC you build the packages and they are placed in the repository on the USB drive. Then on your other machine you add the repository and install any AUR packages that you added to the repository from there. Dependency resolution would be handled by pacman itself just like for the normal repositories.

aurutils

Check out aurutils, it is a collection of scripts that helps to streamline the process of maintaining a custom-repo for you aur packages. It takes a little to set everything up in the beginning (but it is less work then OPs method). After the initial setup everything just works.

I have yay installed but I've also setup aurutils on my server that automatically builds a list of packages to a pacman repo every day so I can just update them with my other pacman packages. Saves time compiling them during updates and lets me upgrade the same packages on my desktop and laptop without having to needlessly build them twice.

I have the opposite feeling. Upgrading kernel requires rebooting, or kernel modules is unable to work. That's annoying. Currently I use kernel-modules-hook to prevent rebooting on Arch.

You can use this pacman hook so that old modules survive a kernel update https://github.com/saber-nyan/kernel-modules-hook

It’s a good idea to reboot ASAP after installing a kernel update anyway, but to keep things running smoothly in the meantime, I recommend installing the kernel-modules-hook package and enabling its systemd service, which keeps the current kernel’s modules available until after the next reboot. (Details here.)

Use https://github.com/saber-nyan/kernel-modules-hook to fix this. It only happens because the package manager completely removes the modules for the current kernel from the filesystem, so you can't load them anymore.

In regards to the “Core parts of the system have been upgraded, a reboot is recommended” notifications, those don’t really mean you need to reboot then. Sometimes I go through two or three minor kernel updates before rebooting my machine. You will rarely encounter things that break without a restart after “core component” updates, and if you install kernel-modules-hook from the repos, the amount of issues you’ll run into after updating will be close to zero. I’ve only encountered this kind of issue once with that package installed, and without it it’s fine too, you’ll just have to reboot if you want to do something like modprobe after a kernel update.

FWIW, kernel-modules-hook is really slow because it depends on rsync, and it rsyncs everytime the hook is fired. https://github.com/saber-nyan/kernel-modules-hook/issues/14 https://github.com/saber-nyan/kernel-modules-hook/pull/15

Thanks for this! I'll switch from kernel-modules-hook and see how it goes.

If you're talking about kernel-modules-hook, haven't you enabled the systemd service to cleanup the old modules as mentioned in the GitHub repo's README?