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.

  • HybridSarcasm@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    51
    arrow-down
    5
    ·
    edit-2
    3 days 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.

    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.

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      No, package installers support configuration. Plenty of packages (e.g. postfix) prompt for configuration at install time.

    • splendoruranium@infosec.pub
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      2 days 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.

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      13
      ·
      3 days 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.