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,
Paul, thank you very much
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
Hi,
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
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
On 8/11/07, D. Krmpotic [EMAIL PROTECTED] wrote:
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
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
