sam6816

I agree, but such a section already exists. _4. XBPS Package Manager_ and _4.1 Advanced Usage_. It starts with an overview of the xbps-commands. The descriptions contain "...can also remove...

This is another issue gravitating around xbps/advanced-usage.md. And it shows the connection to man pages. There is some overlap, but of course man pages are technical (written rather by devs),...

I guess we agree that "Update" with `xbps-install -Su` is the first and most important message in the XBPS section. And at the same time it is _the_ way to...

It all shows in this core message, right after the xbps-command list: > **Updating** > > Like any other system, it is important to keep Void up-to-date. Use xbps-install(1) to...

The guidelines say: > Outside of the 'installation' sections, step-by-step instructions containing 'magic' commands for copying-and-pasting are strongly discouraged. Users are expected to read the **canonical documentation (e.g. man pages)**...

Good idea. My connecting point would be "Virtual Packages" (in 4.1 Advanced Usage) and **xbps-create** (not listed). I am not at all against a whole page. But the handbook should...

It is not a duplication when you just mention/link it for completeness sake. I thought xbps-create could be used to kind of extend the virtualpkg= functionality. Another open issue 631...

Oh well, I just saw it already is there, the link to void-packages README.md! Between xbps.d link and "Updating". "To learn how to build packages from source..." xbps-src is mentioned...

Not directly I'm afraid...I guess "PR" is pull request, so doesn't that mean you are expecting a (first) fix from me? (sorry I don't check my email every day)