>On Tue, 2006-01-10 at 09:00 -0800, Daniel B. Thurman wrote: >> Problem here is that when one wants to install a 'feature', then >> in most cases these are installed in the features and >plugins folders, > >An Eclipse feature is a collection of Eclipse plugins. > >> and other places - so what is not clear - is if there is any >"dangers" >> in doing this - in cases where it *might be possible* to overlay the >> files that are FCX ports. > >Now I'm confused :) What do you mean? > Ok, what I mean - is say that I manually install the WST bundle into the /usr/share/eclipse area; the files packaged in this bundling is going to be installed so I have no idea if any if the files that is pre-existing is going to be overwritten - so in this case I am ASSUMING that this was all figured out beforehand and is OK. This is is also ASSUMING that the FC port does not have any files there that *might* get blown away - the end result is a broken or fluttering eclipse installation. >This is an issue with all of our java packages. Our specfiles are >mostly derived from JPackage ones with changes going both ways between >them and ours containing the native-compilation bits. I'm actually >surprised that your latest update came from JPackage. I would have >thought that your problem was due to our latest FC update which has this >issue: > >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177210 The way I discovered this, was that I completely removed the eclipse files (using yum groupremove) and manual forced deletions in attempts to remove eclipse - followed by a yum update and only two files were downloaded and installed directly from jpackage: 1) eclipse-rcp-3.1.1-1jpp_1fc.FC4.12 2) eclipse-jdt-3.1.1-1jpp_1fc.FC4.12 What I do recall - is that without the rest of the "support files" in place - everything just went to heck. SO - that is why I made the decision to "start over clean" and could NOT do it any other way except to use the groupremove/groupinstall. All other attempts to use yum resulted with these two files - the rest from FC/redhat just would not be included. Once I got the other files installed - I was able to get back my virgin eclipse package and it all runs now sans deep testing. The following is my current list: eclipse-bugzilla-0.1.0_fc-16 (u) eclipse-cdt-3.0.0_fc-1.FC4 eclipse-changelog-2.0.1_fc-21 (u) eclipse-ecj-3.1.1-1jpp_1fc.FC4.12 (u) eclipse-jdt-3.1.1-1jpp_1fc.FC4.12 eclipse-pydev-0.9.3_fc-7 (u) eclipse-platform-3.1.1-1jpp_1fc.FC4.12 (n) eclipse-rcp-3.1.1-1jpp_1fc.FC4.12 The following are the rpms in the fc4 distro directory, so you can see the changes yourself when jpackage is involved: eclipse-bugzilla-0.1.0_fc-16.i386.rpm eclipse-cdt-3.0.0_fc-0.M6.7.i386.rpm eclipse-changelog-2.0.1_fc-21.i386.rpm eclipse-ecj-3.1.0_fc-0.M6.22.i386.rpm eclipse-jdt-3.1.0_fc-0.M6.22.i386.rpm (d) eclipse-jdt-devel-3.1.0_fc-0.M6.22.i386.rpm (d) eclipse-pde-3.1.0_fc-0.M6.22.i386.rpm (d) eclipse-pde-devel-3.1.0_fc-0.M6.22.i386.rpm (d) eclipse-platform-3.1.0_fc-0.M6.22.i386.rpm (d) eclipse-platform-devel-3.1.0_fc-0.M6.22.i386.rpm eclipse-pydev-0.9.3_fc-7.i386.rpm Legend: (u) - Updated (n) - New (d) - Deleted (?) - Not clear Kind regards, Dan -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 1/9/2006
