I prefer lists to always be one item per line and in alphabetical order.
One item per-line makes merge conflicts less likely in the future.
Alphabetic ordering should mean any duplicate entries become obvious to
a human adding items.
Other orderings that future editors can easily spot and comply with are
fine and if there is a good reason to keep stuff bunched up (saving your
scroll wheel is not one) then that is fine too. I just use this as a
"Do the following by default" guideline.
Copy the current set of required packages from
https://github.com/debauchee/barrier/wiki/Building-on-Linux
sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev \
libavahi-compat-libdnssd-dev libssl-dev libx11-dev \
libqt4-dev qtbase5-dev
This is following a failure of:
E: Unable to locate package libxtst-dev
From the AppVeyor build. The Travis build is debian, the AppVeyor one
is Ubuntu 18.04 at present.
Syntax errors behave strangely when the yml parser stops being involved
and Power Shell or Bash take over. This error said:
sh sudo apt-get update && sudo apt-get install \ libxtst-dev
qtdeclarative5-dev libavahi-compat-libdnssd-dev
sh: 0: Can't open sudo
Command exited with code 127
When I pushed AppVeyor reported:
Error parsing appveyor.yml: "environment" section must be a mapping.
(Line: 7, Column: 13)
I assume this means they cannot be empty. I had left only commented out
lines in it.
The AppVeyor system does not work in my fork of the project. To make
the build common between forks and the main, a .yml file should be used.
Outline the sections and basics in some comments as described in the
AppVeyor getting started notes. Copy the build steps from the current
.travis.yml file.
Once the Linux builds are working, I can start guessing at how to get
the Windows one running as well.
Thomas A. F. Thorne