[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1599) Dependency on Gnome not documented?

[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1599 at 4/18/11 3:30 PM: ----------------------------------------------------------- Notice how there's a "gtk" in JBDS installer jar filename? That's not accidental. Eclipse on linux needs GTK. Sorta like Eclipse on Mac requires Cocoa (or previously Carbon). For extreme details on what Eclipse (and therefore JBDS) needs, see: http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32- and 64-bit, GTK 2 only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32- and 64-bit, Cocoa only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32-bit Windows only) or http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclip... As to RPM packaging, no, that wouldn't make things easier since we'd then need 14 installers, not 10. If we get to the point where we have two multi-platform installers (one w/ EAP, one without), then yes, wrapping RPM around that is not unreasonable. But adding 40% more packages (and disk footprint on servers for building/staging/publishing) is not reasonable at this time. was (Author: nickboldt): Notice how there's a "gtk" in JBDS installer jar filename? That's not accidental. Eclipse on linux needs GTK. Sorta like Eclipse on Mac requires Cocoa (or previously Carbon). For extreme details on what Eclipse (and therefore JBDS) needs, see: http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32- and 64-bit, GTK 2 only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32- and 64-bit, Cocoa only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32-bit Windows only) As to RPM packaging, no, that wouldn't make things easier since we'd then need 14 installers, not 10. If we get to the point where we have two multi-platform installers (one w/ EAP, one without), then yes, wrapping RPM around that is not unreasonable. But adding 40% more packages (and disk footprint on servers for building/staging/publishing) is not reasonable at this time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira