Re: How to install Eclipse 3.5 on Debian 5 (lenny) stable release ?

[Tsang Kim Wai <tkwinfo@gmail.com>]

Hi All,

     Thanks for all your information. The eclipse 3.5 works OK.

     But if I want to try one of Mathias suggestion to upgrade my old eclipse 3.2 to eclipse 3.4 in the unstable release, then, in my understanding, I would need to edit the "/etc/apt/sources.list" file to change any "lenny" keywork to "sid". 

     My sources.list file contains the following lines :

deb http://ftp.hk.debian.org/debian/ lenny main contrib non-free
deb-src http://ftp.hk.debian.org/debian/ lenny main contrib non-free

deb http://security.debian.org/ lenny/updates main contrib non-free
deb-src http://security.debian.org/ lenny/updates main contrib non-free

deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free

     Then I think replacing all "lenny" to "sid" should change my Debian system from stable to un-stable release so that I could upgrade eclipse 3.2 to eclipse 3.4 by running just "apt-get install eclipse". Is that the case ? 

     Alternatively, if I don't change my Debian system to un-stable release through editing "sources.list", could I still upgrade my old eclipse 3.2 to eclipse 3.4 in other way ?

     Any comment / suggestion.

Regards
Lawrence

On Mon, Jan 11, 2010 at 1:54 AM, Mathias <m9236@abc.se> wrote:

On Sun, 10 Jan 2010, Tsang Kim Wai wrote:

Hi Nick Douma, Liam O'Toole and Mathias,

     It works by simply extracting the downloaded Eclipse 3.5 binary file
into /usr/local/eclipse-3.5/ directory and then run the eclipse script under
that directory. But I think, the eclipse 3.5 simple installation may depend
on some configurations of my old eclipse 3.2 installation. That is, I may
not un-install eclipse 3.2 while expecting eclipse 3.5 would work properly.
Is that the case ?

     Anyway, thank you for all your suggestions.

Yeah, seeing how the apt system on debian mostly works to maintain and upgrade the packages to newer version, the 3.4 that is in unstable would replace the 3.2 one, unless some changes were made to the newer package.

As mentioned earlier, creating a symlink in /usr/bin seems like a good idea too.

Mat