external-applications.md: Add section on Steam

[cinerea0]

This commit adds the relevant and current information from the Steam wiki page to the External Applications handbook page.

[cinerea0]

@ericonr Is this something that would be considered for inclusion, or is the post-install message sufficient for documenting this?

[ericonr]

I dislike having information split between places, so I'd prefer to have all of it either here or in void-packages. The information in void-packages I want to move to a README.voidlinux file, btw (this would also allow it to be more verbose, so some of the new text from here could go there).

@Chocimier what do you think? How should we determine what goes in void-docs and what goes in a readme file for the package?

[ericonr]

Kind of unrelated, but I think we could add a tiny item to the XBPS part about seeing install msgs (xbps-query -p install-msg <package>), and this would link there instead of to the git repo.

[ericonr]

After some more thinking, maybe the README could really only mention libraries and this section should mention the actual workarounds etc.

[Chocimier]

How should we determine what goes in void-docs and what goes in a readme file for the package?

This is question about scope of void-docs, will leave decision to you.

Readmes can contain anything, no idea how far from "system components" like network or printing docs should go.

[cinerea0]

@ericonr Can you elaborate on what the README.voidlinux files are or will be? That'll help a lot in me having an opinion on where things should go.

[ericonr]

@cinerea0 see https://github.com/void-linux/void-packages/blob/master/Manual.md#void-specific-documentation and the existing README.voidlinux files in void-packages :)

The idea is to leave printing things to the terminal during installation for important messages, and have actual docs available but without bumping the actually important stuff from view :)

[cinerea0]

@ericonr Okay, I think I understand. In that case, how about, in addition to the current info in the steam install message being moved to a README.voidlinux file, the information specific to the native package in the changes I proposed be moved there as well. I'd still like to keep a Steam section in the docs for the Flatpak version, with a reference to the README file for people using the native package, because the information we had in the wiki that I copied here appears to be difficult to find otherwise. Does that sound reasonable?

As a side note, I was unaware of the functionality of xbps-query you mentioned earlier. Do you think an overview of the -p option might be a valuable addition to the docs?

[ericonr]

I think that does sound reasonable, yes!

As a side note, I was unaware of the functionality of xbps-query you mentioned earlier. Do you think an overview of the -p option might be a valuable addition to the docs?

Definitely! It's not exactly easy to find out about it :)

[cinerea0]

@ericonr Alright, the proposed changes to the steam package have been merged into void-packages. Does the wording in my most recent push look okay?

[cinerea0]

@ericonr Alright, I've incorporated your changes. Also, I made sure check.sh passed before pushing, the error from Travis is just it being unable to contact zeroconf.org at the time.

[cinerea0]

Failing check is because it couldn't connect to libressl.org. God, travis sucks for connectivity. I ran check.sh locally before pushing and it didn't return any errors.

[ericonr]

Great, thanks!

And yes, we should look into using GH actions.