So, I don’t know where this matter might fall in terms of it being an issue with topgrade, an issue with uBlue, or an intended configuration change, but… well, here goes.
So, topgrade’s documentation says “Files in $CONFIG_DIR/topgrade.d/ are automatically included before this file” in the section about included files. The example also doesn’t show anything included that implies you have to manually add this directory as a search path, so naturally, I take that to mean topgrade always checks for files there.
Well, I went ahead and added a simple config to update “AM”, tested, and… nothing. So, configs in topgrade.d don’t seem to be loaded. Can anyone tell be just where in the pipeline this matter lies so I can deal with it? I’m really hoping I’m not going to be forced to change the update verb in ujust for this, because I don’t want to have to live paranoid that some update is going to break the new verb I add.
I’m on Bazzite desktop, but since I was just asking where in the pipeline I actually need to make this change, I didn’t figure it would be that different. I know the actions of ujust can be different between the images, but unless there’s a fundamental difference in how the whole thing works, I didn’t figure it would come up.
For now, I’m just trying to add AM updates to topgrade as triggered by ujust update, like I said. If that’s dealt with, then realistically, any other topgrade change should fall in if necessary, but I don’t currently have any plans for any other changes.