In general, you should always go with the package unless you need a more
recent version for some reason. Using the version that’s packaged for
your
distribution means that it will upgrade automatically (including
security
updates), you’ll be sure it’s using the right version of shared
libraries,
and it’s much easier to install and remove.
The version of nginx in ubuntu feisty is 0.4.13 ( Ubuntu – Error ) and the most recent
version of
nginx is 0.5.30. If 0.4.13 is good enough for you then I’d use that.
Check
the changelog ( http://nginx.net/CHANGES-0.5 )
BTW, I’d recommend using aptitude instead of apt-get, it handles
dependencies better.
There is no nginx package for 6.06, afaik (at least not in main,
universe, or multiverse). I have just set up a fresh 6.06 system, and
I downloaded the 0.5.30 (latest) nginx source, and built with the
standard ‘./configure && make’ - then ‘sudo make install’. No
problems, and works fine for me. You will need ‘sudo aptitude install
build-essential’ first, though, to get gcc and related build
utilities.
yes, that’s what I was going to do (and probably will).
I want to understand Ubuntu’s package manager philosophy though.
So say that there was a possibility to install nginx to 6.06 via
aptitude, how would they decide when the new version is ready so that
users can reach it via upgrade. And especially why is there a lag
between version in a package and the newest one.
0.5.30 seems pretty old in comparison to 0.4.13 (not that I know a lot
about the differences, only judging from the version number)…
but if I do decide to go with aptitude / apt-get, will 0.4.13 then get
upgraded by aptitude to the next version? what’s the philosophy there…
is there always a few months lag between latest and supported version?
and because this is not the latest version of ubuntu, does that matter?
6.06 is LTS (long-term support) however…
thank you in advance!
PS: I also didn’t know it’s better to use aptitude versus apt-get …
thank you for that tip as well.
David
Paul D. wrote:
In general, you should always go with the package unless you need a more
recent version for some reason. Using the version that’s packaged for
your
distribution means that it will upgrade automatically (including
security
updates), you’ll be sure it’s using the right version of shared
libraries,
and it’s much easier to install and remove.
The version of nginx in ubuntu feisty is 0.4.13 ( Ubuntu – Error ) and the most recent
version of
nginx is 0.5.30. If 0.4.13 is good enough for you then I’d use that.
Check
the changelog ( http://nginx.net/CHANGES-0.5 )
BTW, I’d recommend using aptitude instead of apt-get, it handles
dependencies better.
ok - my general philosophy is to stick with the distro packages
wherever possible - in that way you are sure that the interlocking
mesh of dependencies is (hopefully!) handled correctly, and where
there are major bugs or security issues, then the package is updated
throught the ‘sudo aptitude update’ mechanism. For your source
compiled stuff, you are responsible for keeping it up to date and
secure - which can be a major headache if you have several programs
built from source to maintain.
The downside to using the distro packages is that you may not have
that ‘latest, greatest’ feature you must have.
Distro packages for a particular distro version (eg. 6.06) will not
usually be ‘upgraded’ to a later version - for that, you usually need
to upgrade the whole distro to the newer version.
I you are looking for stability and security, stick with 6.06 - or if
you want to be on the edge, then upgrade to the latest (7.04 ‘feisty’)
I use 6.06 for servers, and have 7.04 on the desktop.
The lag between versions is due to when the distro package list for a
new distro version is locked down prior to release. Any upstream
releases after that date would then only make it into the next distro
version.
I want to understand Ubuntu’s package manager philosophy though.
LTS in 6.0.6 LTS stands for Long Term Support. Ubuntu committed to
support this version until year 2011 (which isn’t really long at all,
considering how many computer systems built in 1970s are still in
production).
The release policy for versions like that is “stability tramps
coolness”. So, the distro maintainers will generally provide bugfixes
and security patches, but won’t upgrade to anything that creates a
risk of incompatibility with apps people are already running.
Which is why RedHat EL 4 is still on Ruby 1.8.1, and Ubuntu 6 on 1.8.4.
I want to understand Ubuntu’s package manager philosophy though.
LTS in 6.0.6 LTS stands for Long Term Support. Ubuntu committed to
support this version until year 2011 (which isn’t really long at all,
considering how many computer systems built in 1970s are still in
production).
The release policy for versions like that is “stability tramps
coolness”. So, the distro maintainers will generally provide bugfixes
and security patches, but won’t upgrade to anything that creates a
risk of incompatibility with apps people are already running.
Which is why RedHat EL 4 is still on Ruby 1.8.1, and Ubuntu 6 on 1.8.4.
So I did install it… everything seemed to go through fine, but I
decided to check for file /etc/init.d/nginx (a few sites mention it)…
and I found out that this file doesn’t exist. Is this something to worry
about or it’s normal somehow? I want to be sure about that before trying
to go further. Thank you!david
So I did install it… everything seemed to go through fine, but I
decided to check for file /etc/init.d/nginx (a few sites mention it)…
and I found out that this file doesn’t exist. Is this something to worry
about or it’s normal somehow? I want to be sure about that before trying
to go further. Thank you!david