I only discovered this recently, and it's very handy.

Piping scripts directly to bash is a security risk. You can always download the scripts, inspect them and run locally if you so choose.

you are viewing a single comment's thread
view the rest of the comments
[–] 46 points 1 year ago* (3 children)

Apples and oranges.

Package managers only install a package with defaults. These helper scripts are designed to take the user through a final config that isn’t provided by the package defaults.

No need to be elitist about such things.

EDIT: this particular repo is highly regarded in the community. It is very akin to the AUR. It’s not some haphazard collection of scripts.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 1 year ago

    Apples and oranges.

    Package managers only install a package with defaults. These helper scripts are designed to take the user through a final config that isn’t provided by the package defaults.

    Whether there's a setup wizard doesn't have anything to do with whether the tool comes from a package manager or not. Run "apt install ddclient", for example, it'll immediately guide you through all configuration steps for the program instead of just dumping a binary and some config text files in /etc/.

    So that's not the bottleneck or contradiction here. It's just very unfortunate that setup wizards are not very popular as soon as you leave Windows and OSX ecosystems.

  • source
  • parent
  • [+] -6 points 1 year ago

    Package managers only install a package with defaults. These helper scripts are designed to take the user through a final config that isn’t provided by the package defaults.

    This is trivially solved by having a "setup" script that is also installed by the package manager.

  • source
  • parent