Okay. I unfortunately need to have a custom kernel/base, and I used the instructions here:
to do that via pkg, and that seems to be working. However, what’s not clear to me is how well pc-updatemanager is going to deal with that, since presumably, when there’s an update, I’m going to need it to update to the new, normal kernel/base and then rebuild the kernel/base for the exact same commit with my changes. When there’s a newer kernel/base in the TrueOS package repo, will it grab those packages and install them? Will it grab the new base packages but not update my kernel, because it’s a different package name (since it has a different KERNCONF)? Will it just not update any of my kernel/base packages, because I explicitly installed them from my local repo?
Basically, is it going to work in some manner to just use pc-updatemanager and then rebuild the kernel/base with my changes after the update, or am I going to have to explicitly reinstall the base/kernel from the TrueOS repo so that I can update cleanly (and then rebuild the kernel/base with my changes after the update)? Certainly, it seems like if I’m not careful here, I’m going to end up with a borked system when I try and update (which would then be revertible via boot environments, but the need to successfully update still remains).