You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After somewhat lengthy discussion on IRC, I'd like to record it here. The proposal is to try and make a single section (possibly even a single page) as reference for all applications that aren't installed via xbps.
This page would:
Be "probably in the installing section, near the existing documentation for nonfree" and "with a paragraph explaining the distinction between nonfree, non-distributable, and proprietary closed-source". @the-maldridge
Tell people to try and use flatpaks for most of their external needs, especially when proprietary (we might need to document flatpak too, if people have issues with it). Probably list a few applications that flatpak allow people to use. @bobertlo
Explain that some language package managers, such as pip and gem (External applications #185) can require the respective devel packages for those languages (so python-devel and ruby-devel) in order to build some libraries. This can be even more relevant when using a musl build.
It seems like this is the intention of this post, but for clarity I will state again that we are interested in a single page explaining common third party application general handling procedures, i.e. using flatpak, and we are not interested in a "section" for long pages covering each application. (i.e. steam #159)
After somewhat lengthy discussion on IRC, I'd like to record it here. The proposal is to try and make a single section (possibly even a single page) as reference for all applications that aren't installed via xbps.
This page would:
What we need, AFAIK:
I wrote this right before going to sleep, so if there are any egregious mistakes I can correct them in a bit.
The text was updated successfully, but these errors were encountered: