Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 173245
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Josh Nichols (RETIRED) <nichoj@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 173245 depends on: Show dependency tree
Bug 173245 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-04-03 13:55 0000
Eclipse has never been marked stable, ppc is back at 3.0.1-r3, and x86 is on
3.2.

There are an absurd number of improvements since the 3.0.x days. There are even
improvements since 3.2, which is when we started using a shared patchset with
several other distros. The most notable is that users can actually use the
update manager to download/install plugins, which would allow us to prune the
ancient plugin ebuilds that are in the tree.

There are a number of eclipse bugs open, but a lot of them refer back to
ancient versions of the package, and most haven't been verified on the lastest
version. By getting rid of those old versions, we'll be able to clean the slate
with the bugs, and be able to focus on issues that are affecting the most
recent versions.

Two issues to be on the look for:
  Some users have had build issues on amd64. Wasn't able to ever reproduce
myself.
  There were some UI issues with swt not working correctly on ppc with
ibm-jdk-bin-1.5, such that it isn't really usable. azureus had experienced this
issue too, but has since been marked stable on ppc, so it seems like this may
no longer be an issue.

------- Comment #1 From Petteri Räty 2007-04-03 14:15:49 0000 -------
(In reply to comment #0)
> Eclipse has never been marked stable, ppc is back at 3.0.1-r3, and x86 is on
> 3.2.
> 

Has never been marked stable on amd64. Please test the update manager to
install some plugins so that we can be sure that we can finally remove the old
binary cruft plugins we have around.

------- Comment #2 From Josh Nichols (RETIRED) 2007-04-03 15:42:48 0000 -------
(In reply to comment #1)
> Has never been marked stable on amd64.

Thanks Petteri, that's exactly what I meant.

I'd also like to mention that I've been using this revision daily on x86 and
amd64 since I bumped it back in October without issue.

------- Comment #3 From Christian Faulhammer 2007-04-06 10:34:11 0000 -------
* QA Notice: Pre-stripped files found:
 *
/var/tmp/portage/dev-util/eclipse-sdk-3.2.1-r1/image/usr/lib/eclipse-3.2/libcairo-swt.so

x86 stable

------- Comment #4 From Joe Jezak 2007-04-07 14:42:00 0000 -------
I can't reproduce the text issue on either azureus or eclipse with the
currently stable ibm jdk / azureus or this version of eclipse.  I tried the
update manager and it seems to work okay too, so I think it's safe for a ppc
stable keyword.

Marked ppc stable.

------- Comment #5 From Daevid Vincent 2007-04-09 22:54:41 0000 -------
I too would like to add a request for this. I'm getting into Ruby/Rails dev and
am a long time LAMP developer, and everyone raves of Eclipse, but I run a
stable system and don't want to get into ~x86 path. I did it once, and it was
fun for a while, but ended up being too painful to maintain. Like a virus,
eventually EVERYTHING started to become ~x86 just to keep current.

------- Comment #6 From Peter Weller 2007-04-12 14:50:44 0000 -------
Stable on amd64, closing

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug