Bug 1286794 - [rfe] split up eclipse.ini file
[rfe] split up eclipse.ini file
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
23
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Alexander Kurtakov
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-30 13:20 EST by Christian Stadelmann
Modified: 2016-11-24 11:47 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-24 11:47:58 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christian Stadelmann 2015-11-30 13:20:54 EST
Description of problem:
I have changed some parameters in eclipse.ini file, including:
--launcher.GTK_version set to 2, because Gtk3 is very slow
--launcher.XXMaxPermSize to 512M
-Xms512m
-Xmx4096m for performance

Every single time eclipse is getting an update I have to manually edit the configuration because version numbers in "-startup" and "--launcher.library" change. These are configuration options a user usually won't change.

On a semantic level I think those contents belong in two different files in different folders. The user-editable config belongs in /etc, e.g. in a file called /etc/eclipse.ini. The version-specific launcher.library and startup options belong somewhere below /usr, probably /usr/share/eclipse.

Is that possible?

Version-Release number of selected component (if applicable):
eclipse-platform-4.5.1-5.fc23.x86_64

How reproducible:
always
Comment 1 Alexander Kurtakov 2015-11-30 13:27:21 EST
Short answer - no, it will require significant effort upstream for not that much benefit as GTK 2 option and MaxPermSize are probably to be gone really soonish.
Comment 2 Mat Booth 2015-11-30 14:43:56 EST
FWIW, perm gen was removed in Java 8 so "MaxPermSize" is ignored, this setting should have no effect on Fedora 23.
Comment 3 Fedora End Of Life 2016-11-24 08:50:56 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.