Re: how to update packages now sarge is stable?
Lee wrote:
hi
I have had sarge installed on a dell latitude c400 laptop for, I
guess, a couple of years - more or less since Sarge moved to
"Testing". I used to use the "testing" tree for apt-get depositories
until a few weeks ago when Sarge was about to go stable at which point
I started using the apt-get alias "sarge" in order to maintain the
transition.
I now find myself with a laptop that is set up exactly how I want it -
I know how it works and it knows me.
What do I now do about package updates? For example, I am running
Firefox version 1.0.4 and version 1.0.5 has now been released. The
depositories still have 1.0.4 available.
It is called repository not depository.
The stable distribution has the unique feature that packages in it will
not be upgraded unless there is a security fix. Only when new stable
version is released and only when you update the machine to that new
stable version then you will have newer packages. So, until etch (the
next stable release) is released, you will not have new version of
firefox in stable. In any case, there will not be a new version of
firefox in sarge (except for a security fix).
When I downloaded the installer for Firefox v1.0.5 from Mozilla it was
clear that it was going to force install into a self-contained /lib
/bin [...] directory tree that bears no relation to where the files
are currently installed within debian.
Will updates such as this continue to be added to the sarge
depositories or is every software update now a manual affair? What is
the best way to manage this process?
If you want the latest versions of a package, you either need to
download their source and compile it yourself or you can run either
testing or unstable. But they will not be as stable as sarge. For more
details on how the 3 debian distributions work, please read the
following FAQ
http://people.cornell.edu/pages/kk288/debian_choosing_distribution.html
hth
raju
--
Kamaraju S Kusumanchi
Graduate Student, MAE
Cornell University
http://www.people.cornell.edu/pages/kk288/
Reply to: