[mitchty]

I started to try to get things running at work. We use SLES at work, needless to say this has to be the most annoying product to setup ever.

Also the setup instructions have everything prefixed with sudo, why they don't just say sudo su - user and do the rest as that user is beyond me. Half of the setup could just be a few sh scripts.

I'm about halfway through the setup, but this project won't see a lot of adoption given its insane dependency hell and installation tedium.

[mnutt]

Also the setup instructions have everything prefixed with sudo, why they don't just say sudo su - user and do the rest as that user is beyond me. Half of the setup could just be a few sh scripts.

In many of the more security-conscious organizations, `sudo` is preferred over `su` because it leaves an audit trail. They could automate parts of that and perhaps they should, but the way they have it now shows you exactly which parts of your system you are modifying. It's a tradeoff; if they didn't, they'd have people scolding them for the install scripts wreaking havoc on their production systems.

[mitchty]

I'm well aware of sudo vs su. Where I work sudo ONLY allows you to run preapproved scripts or if you have permission the ability to su - someuser (- is necessary). Yes I'm an admin and can do "more", but not markedly.

In addition I have to type my password in each time I use sudo, also by policy thanks to things like PCI compliance.

You can show what parts of the system you are modifying, and provide scripts to automate it. They aren't mutually exclusive actions.