Why does eclipse-sdk-3.2.1-r3 require ancient java

[MadEgg]

I just did a sync and and emerge -uDav world. Now emerge want's to do this:

Code: Select all

These are the packages that would be merged, in order:

Calculating dependencies                               ... done!
[ebuild  NSF  ] dev-java/sun-jdk-1.4.2.17  USE="X alsa nsplugin -doc -examples -jce -odbc" 35,525 kB
[ebuild  NS   ] virtual/jdk-1.4.2  0 kB
[ebuild     U ] dev-util/eclipse-sdk-3.2.1-r3 [3.2.1-r2] USE="cairo gnome opengl -branding -seamonkey" 67,667 kB

Total: 3 packages (1 upgrade, 2 in new slots), Size of downloads: 103,191 kB
Fetch Restriction: 1 package (1 unsatisfied)

Would you like to merge these packages? [Yes/No] n

Quitting.

Why on earth does it want to install an ancient java JDK on my machine? In the ebuild it says something about forcing 1.4 for building, but why? Eclipse works just fine here being built with 1.6 so why would it need to be built with 1.4.2?

[CooSee]

I just did a sync and and emerge -uDav world. Now emerge want's to do this:

Code: Select all

These are the packages that would be merged, in order:

Calculating dependencies                               ... done!
[ebuild  NSF  ] dev-java/sun-jdk-1.4.2.17  USE="X alsa nsplugin -doc -examples -jce -odbc" 35,525 kB
[ebuild  NS   ] virtual/jdk-1.4.2  0 kB
[ebuild     U ] dev-util/eclipse-sdk-3.2.1-r3 [3.2.1-r2] USE="cairo gnome opengl -branding -seamonkey" 67,667 kB

Total: 3 packages (1 upgrade, 2 in new slots), Size of downloads: 103,191 kB
Fetch Restriction: 1 package (1 unsatisfied)

Would you like to merge these packages? [Yes/No] n

Quitting.

Why on earth does it want to install an ancient java JDK on my machine? In the ebuild it says something about forcing 1.4 for building, but why? Eclipse works just fine here being built with 1.6 so why would it need to be built with 1.4.2?

add ' java5 ' to your make.conf

CooSee ' Ya

[jonnevers]

Why on earth does it want to install an ancient java JDK on my machine? In the ebuild it says something about forcing 1.4 for building, but why? Eclipse works just fine here being built with 1.6 so why would it need to be built with 1.4.2?

The "forced" part is because portage can not link directly to propriety binary blobs. If allows you to emerge them but you have to bring the tarball down yourself. This is the case with JDK 1.4.2.

I've been using eclipse-3.2 with JDK 1.5 and it does work fine.

why not just stop using an ancient version of eclispe? 3.3 is the current stable and depends on java5 or higher.

[MadEgg]

I just did a sync and and emerge -uDav world. Now emerge want's to do this:

Code: Select all

These are the packages that would be merged, in order:

Calculating dependencies                               ... done!
[ebuild  NSF  ] dev-java/sun-jdk-1.4.2.17  USE="X alsa nsplugin -doc -examples -jce -odbc" 35,525 kB
[ebuild  NS   ] virtual/jdk-1.4.2  0 kB
[ebuild     U ] dev-util/eclipse-sdk-3.2.1-r3 [3.2.1-r2] USE="cairo gnome opengl -branding -seamonkey" 67,667 kB

Total: 3 packages (1 upgrade, 2 in new slots), Size of downloads: 103,191 kB
Fetch Restriction: 1 package (1 unsatisfied)

Would you like to merge these packages? [Yes/No] n

Quitting.

Why on earth does it want to install an ancient java JDK on my machine? In the ebuild it says something about forcing 1.4 for building, but why? Eclipse works just fine here being built with 1.6 so why would it need to be built with 1.4.2?

add ' java5 ' to your make.conf

CooSee ' Ya

But as you can see eclipse-sdk does not use a JAVA5 USE-flag, and besides, it worked before. Why would anyone introduce a function to compile eclipse with an ancient Java-version anyway? I mean, Java 1.4.2 is in it's EOL period to october the 30th, so it's a little late to add support for that, don't you think?

[jonnevers]

considering how good eclipse's built in software manager is, its worth just getting it from eclipse.org and untarring it into /opt/eclipse or wherever and calling it a day.

[timeBandit]

considering how good eclipse's built in software manager is, its worth just getting it from eclipse.org and untarring it into /opt/eclipse or wherever and calling it a day.

++
Eclipse is nicely self-contained and its plugin/update manager is too good not to use, but using it will only confuse Portage. So why bother with Portage in the first place? This type of installation is one of the reasons for /opt, after all.

[alistair]

considering how good eclipse's built in software manager is, its worth just getting it from eclipse.org and untarring it into /opt/eclipse or wherever and calling it a day.

++
Eclipse is nicely self-contained and its plugin/update manager is too good not to use, but using it will only confuse Portage. So why bother with Portage in the first place? This type of installation is one of the reasons for /opt, after all.

Seeing that /opt is for system/portage installed binary packages, that statement is incorrect.

[timeBandit]

I beg to differ:

/opt is reserved for the installation of add-on application software packages.
...
Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator.

Portage's use of /opt for binary packages is one valid use, not the only one. Agreed that it's generally preferred to use an ebuild when available, but it's not universally the best option.

[jonnevers]

Portage's use of /opt for binary packages is one valid use, not the only one. Agreed that it's generally preferred to use an ebuild when available, but it's not universally the best option.

welllllll, what the person is saying is that /usr/local is a more traditional place for this sort of thing.

my opinion, is that its a waste of time to even think about. it's my computer, i have root, it's my filesystem, and i prefer /opt for easy access.

i knew someone was going to bring it up... it could be argued that at some point something named 'eclipse' may get installed by portage into /opt/eclipse. <shrugs>

[alistair]

Portage's use of /opt for binary packages is one valid use, not the only one. Agreed that it's generally preferred to use an ebuild when available, but it's not universally the best option.

welllllll, what the person is saying is that /usr/local is a more traditional place for this sort of thing.

my opinion, is that its a waste of time to even think about. it's my computer, i have root, it's my filesystem, and i prefer /opt for easy access.

i knew someone was going to bring it up... it could be argued that at some point something named 'eclipse' may get installed by portage into /opt/eclipse. <shrugs>

Yes it could be argued. and is it that much harder installing into /usr/local than /opt?

[psdasilva]

I tried to add java5 to USE in make.conf, then droped java, changed to java6 and it still wants to install java-1.4.2.17!!!

Anything more to try?

Thanks

[alistair]

I tried to add java5 to USE in make.conf, then droped java, changed to java6 and it still wants to install java-1.4.2.17!!!

Anything more to try?

Thanks

more "dev-java/eclipse-sdk ~<arch>" >> /usr/portage/packages.keywords

[psdasilva]

more "dev-java/eclipse-sdk ~<arch>" >> /usr/portage/packages.keywords

You mean a new version of eclipse? I don't need it to the extent of going to an unstable version.

I built eclipse, unmerged virtual/jdk-1.4.2 and then ran emerge --depclean.

Thanks anyway.