It would help with automating the process of compiling the latest nginx.
Also, there is a lot of documentation on the web that explains how to
get and compile nginx from sources and all these docs become obsolete
over time because they point to the nginx that was available during
the time of writing the doc.
On Fri, Sep 28, 2012 at 02:14:42PM +0200, Jan Wrobel wrote:
Also, there is a lot of documentation on the web that explains how to
get and compile nginx from sources and all these docs become obsolete
over time because they point to the nginx that was available during
the time of writing the doc.
I don’t like this aproach as it makes impossible to determine
version from a downloaded file name, and makes it impossible to
determine what will be overridden on archive extraction without
looking into archive contents. And one would need a version
number for automated processing anyway, as it’s embedded into
directory structure in release archives.
Something like: http://nginx.org/download/nginx-current.tar.gz?
determine what will be overridden on archive extraction without
looking into archive contents. And one would need a version
number for automated processing anyway, as it’s embedded into
directory structure in release archives.
You would still be able to download the archive with the version
number (the current way).
Here is how you can use such link for automated processing: download
nginx-current.tar.gz to an empty directory, extract it (nothing is
overridden, the directory is empty), cd to nginx* (the only operation
that uses the version number); compile and install (no version number
needed)