3 ms·

> Our installer is capable of automatically installing dependencies on current versions of So you dirty the system where its supposed to be installed, a server

by antocv 10y ago

> Our installer is capable of automatically installing dependencies on current versions of So you dirty the system where its supposed to be installed, a server, with gcc, make and friends? > . If you're running something else it prints out "This doesn't appea State so on your documentation/page before telling the user curl | bash, as I wrote in another post here, that is nice. Your script does not support transactionional installations, as it is it can break at any point in the script and leave the target system broken/dirty. With a simple PKGBUILD youd also have solved the "binary ABI" part. If it really is tedious to coordinate with several distros, you can take a shortcut and dont deliver a "pkgspeed-for_nginx_module-1.2.3@v1.2" package but instead a "pkgspeed-1.2.3" which conflicts with the normal nginx package and thats it.

cbr 10y ago
So you dirty the system where its supposed to be installed, a server, with gcc, make and friends? That's the way nginx is traditionally installed, and we're shipping an nginx plugin. State so on your documentation/page before telling the user curl | bash The first thing the install script does is check if you're on a supported system, and if not it exits. Since the vast majority of people running the script are on supported systems, this seems better than putting a lot of warnings up front. Your script does not support transactional installations, as it is it can break at any point in the script leave the target system broken/dirty By default the script only builds ngx_pagespeed, and doesn't install it. If you ask it to handle the install, it call's nginx's "make install", which again is the standard way you install nginx.
- antocv 10y ago
  > That's the way nginx is traditionally installed No. That is not how nginx is traditionally installed. You misunderstand basic Linux package management and build systems, which is why you end up in this mess. But thats okay, world is keepin on spinnin. To each their own.

by antocv 10y ago

cbr 10y ago

So you dirty the system where its supposed to be installed, a server, with gcc, make and friends? That's the way nginx is traditionally installed, and we're shipping an nginx plugin. State so on your documentation/page before telling the user curl | bash The first thing the install script does is check if you're on a supported system, and if not it exits. Since the vast majority of people running the script are on supported systems, this seems better than putting a lot of warnings up front. Your script does not support transactional installations, as it is it can break at any point in the script leave the target system broken/dirty By default the script only builds ngx_pagespeed, and doesn't install it. If you ask it to handle the install, it call's nginx's "make install", which again is the standard way you install nginx.

antocv 10y ago
> That's the way nginx is traditionally installed No. That is not how nginx is traditionally installed. You misunderstand basic Linux package management and build systems, which is why you end up in this mess. But thats okay, world is keepin on spinnin. To each their own.