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. hth, Tony On 11/08/07, D. Krmpotic <[EMAIL PROTECTED]> wrote: > > 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. > > thank you, > david > -- > Posted via http://www.ruby-forum.com/. > > > > -- Tony White Speechnet Technologies Ltd --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
