Closed issue by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/32833

Description:
Suppose I want to pin my kernel to 5.10, which is the latest LTS.

I can configure
```
virtualpkg=linux:linux5.10
virtualpkg=linux-headers:linux5.10-headers
```
in xbps.d. This works fine in the sense that `linux5.10` will be installed instead of `linux5.13` and it is future proof (contrary to `virtualpkg=linux5.13:linux5.10` which will break when kernel is switched to 5.14).

However, this results in the `linux-base` package as orphan. Of course, I can just change `linux-base` to manual and be done with it, but if I forget this could lead to a broken system and it is more steps to document (and since this is not documented, I don't know if something will change in the future that breaks my system).

I wonder if it would make sense to have a different meta package, say `linux-kernel`, whose only purpose is to depend on `linux${version}`, just like `linux-headers` only purpose is to depend on `linux${version}-headers`.

Then `linux` would be a meta package that depends on `linux-kernel` and `linux-base` (or the actual dependencies as linux-base might become superfluous), and linux kernel version can be pinned easily with virtualpkgs as above. This seems robust enough to be documented in the manual, etc.

---

In fact, it seems the current `linux-base` pkg could just be renamed `linux` adding `linux-kernel` dependency, and the current `linux` could just be renamed `linux-kernel`, keeping `linux-headers` as a subpkg of `linux-kernel`.