esc_ctrl[m] has quit [Quit: Idle timeout reached: 172800s]
redstarcomrade has joined #glasgow
redstarcomrade has quit [Read error: Connection reset by peer]
nstandart[m] has joined #glasgow
<nstandart[m]>
bit of a brainwave; how likely is it that as time goes on, we might need to run some actions after the glasgow tooling is installed, be it adding udev rules, or generally anything that might require manual intervention and/or higher privileges - would it be a good call to remove the current steps from the documentation, and condense them into one command to run, no matter the platform? (eg glasgow post-install)
<nstandart[m]>
maybe also have it automatically perform a sanity check at the end that the tooling can indeed see the hardware
tom has quit [Remote host closed the connection]
<nstandart[m]>
by default, pipx installs programs only for the current user
WilfriedWonkaKla has joined #glasgow
<WilfriedWonkaKla>
Not a good idea. If you install glasgow with pipx, it might not be runnable for a superuser or with sudo.
<nstandart[m]>
you'd have to add --global to have it do what you just said
redstarcomrade has joined #glasgow
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
mei[m] has joined #glasgow
<mei[m]>
that particular thing can be solved with --dry-run
<mei[m]>
could print "Would run the following commands:" so you can do it manually, even
galibert[m] has joined #glasgow
<galibert[m]>
glasgow post-install | sudo sh ?
<nstandart[m]>
not really cross-platform, and that was half the point of doing such a thing