I haven't actually looked at it properly but from what I can tell "virtualbox" package is the one for LTS headers, while Solus 4 ships with Current headers, is this being considered changed at all?
I was initially a bit confused until I read a post somewhere on here about the two packages 
Well, there is the exhaustive guide in the help center, which is also mentioned in the package description:
VirtualBox is a free powerful open source solution for running other x86 and x86_64 operating systems virtually on your computer.
Installation Guide: https://getsol.us/articles/software/virtualbox/en/
edit: I CAN understand people being a bit confused though. Have seen it a number of times (that's why I added the reference to the package description in the first place, to make it a bit more obvious)
Staudey I'm wondering if changing the package would break anyone on older Solus versions using LTS kernels?
I think changing the package name structure at this point would be opening a huge can of worms.
Staudey Yeah, I suspected that. What would be pretty neat is if the package manager could automatically select the right package for the system's kernel regardless with some sort of check, and I somewhat wonder if eopkg is capable of that in the way it's designed. I don't think such a thing is worthy enough to warrant changing the package manager's code to compensate too but it'd save confusion from people who didn't entirely "RTFM" as people sometimes said back in the day...
chillyfairy Solus follows the same naming convention everywhere. All kernel modules for the LTS kernel have no suffix while modules for the CURRENT kernel are suffixed with -current. See here for some more similar packages.
Originally the only kernel available was a LTS kernel (thus no suffix were needed). Later, CURRENT kernel was added in the repository but LTS was still the default, so the new packages that contain modules for the current kernel were suffixed -current while the existing packages kept their original name. That's why they are named this way.
kyrios Thanks for the explanation, I guess this can be closed now and marked as "no" 
