You are not logged in.
Happiness Engineer @ System76
Arch Linux + GNOME
[img]https://i.imgur.com/ZrQGJ9u.jpg[/img]
Offline
Speaking just of the general script aspect ... there are a lot of arbitrary sleeps, I would remove all of those.
You could echo a prompt for what the command is just before the sudo commands, so they know what command they are entering their password for.
You could add a line at the top, "set -e", to tell the script to exit if any of the commands fails
Last edited by chaseleif (2021-02-20 17:57:57)
Offline
Most of the sleeps are so that the user can see what is happening on screen. I think it would be best to just leave the ones around starting services for ones that need to do that using systemd. The 'set -e' sounds like a good idea as well. Thanks!
Happiness Engineer @ System76
Arch Linux + GNOME
[img]https://i.imgur.com/ZrQGJ9u.jpg[/img]
Offline
So all it's really doing is installing half a dozen aur packages - don't do that. Just give interested users the list of packages. If they are unable to install them on their own, there are far bigger problems.
You could make a meta-package if you really wanted.
Last edited by Trilby (2021-02-21 22:06:36)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Perhaps a meta package for each laptop model? For example, system76-serw12-meta.
Offline
@Trilby : This is more useful for setting up the install of these packages quicker for my after my install is done.
@yochanamarqos : That would be nice though it would need to include the other AUR packages in itself which I'm not sure how it works with AUR packages.
Happiness Engineer @ System76
Arch Linux + GNOME
[img]https://i.imgur.com/ZrQGJ9u.jpg[/img]
Offline
@Trilby : This is more useful for setting up the install of these packages quicker for my after my install is done.
If you are using this more than once then you'll already have the compiled packages saved somewhere, just install them using pacman.
Offline
Just create a metapackage then upload that and the dependencies to an openSUSE Build Service repository so you can install everything in one fell swoop.
Para todos todo, para nosotros nada
Offline
Or if nothing else, at least install all the required dependencies first, then build all the packages, and install them all when they are all built. There should only be two interactive steps requiring a user password: install the dependencies, and install the built packages. As is, it could prompt the user for a password almost two dozen times at effectively random intervals, that'd be kinda' a PITA.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline