Hi! I maintain a "curl | bash" installer script [1][2].

    such as only working on specific variants of Ubuntu,
    with specific packages installed in specific version,
    and/or RedHat

Our installer is capable of automatically installing dependencies on current versions of Debian, Ubuntu, and CentOS. If you're running something else it prints out "This doesn't appear to be a deb-based distro or an rpm-based one. Not going to be able to install dependencies. Please install dependencies manually and rerun with --no-deps-check.", which seems pretty reasonable to me?

    submit this data to that platform as an
    debian/{control,etc} to make a .deb or specfile for
    .rpm or PKGBUILD or whatever, and use the platforms
    _build tools_ to generate a platform specific package
    - be a package mantainer if you have to

Building a binary package for ngx_pagespeed isn't really practical. It needs to depend on nginx, but nginx doesn't have an ABI, so it needs to be built from source alongside your existing nginx or as part of a new nginx install. Getting into the distributions, so that they can build the ngx_pagespeed module at the same time as they build their main nginx would work, and is somewhere I would like to be eventually, but requires a lot of coordination with distros.

    Another side effect of telling your users to curl | bash,
    is I wont ever use your software. You didnt make the
    effort to do the right thing with packaging, why would
    you have done any better for whatever it is youre trying
    to do with your shit software?

I do think what we've done in this case is "the right thing" in terms of how we should be spending our development time. Our installation page does still offer manual install instructions, however, for people who would rather not run a script.

[1] https://developers.google.com/speed/pagespeed/module/build_n...

[2] https://ngxpagespeed.com/install