[gentoo-java] Moving Eclipse-3.3 to tree

[gentoo-java] Moving Eclipse-3.3 to tree

[Jean-Noël Rivasseau]

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hello all,

At this point all the dependencies for Eclipse were moved to main tree (they
use the osgi eclass so they make suitable jars for Eclipse). So there is
only now for Eclipse itself to be moved there.

Just wanted to check that junit-4.4-r1, which was also moved to tree, does
not trigger circular dependencies anymore (I checked on the bugzilla and it
seems it is ok).

For information I plan to move it as 3.3.1.1, deleting the ebuilds in the
experimental overlay except the ali_bush latest one (-r2).

Finally I need advice on the following (which is the only thing left to be
done on my agenda before putting Eclipse in tree):

I would like to offer the possibility for the user to control the Eclipse
startup options. Especially regarding the memory options as the default ones
make Eclipse run very slowly, crashing a lot especially on amd64.

Normally this is done by writing options to /usr/lib/eclipse-3.3/eclipse.ini,
but I was thinking of providing a configuration file in /etc/conf.d because:

1) It looks a better Gentoo way (eg, users know about /etc/conf.d, they may
not know about eclipse.ini)
2) It would have a simpler configuration syntax (pure familiar Bash syntax
resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the syntax in
the eclipse.ini file is more obscure even for me - looks like there should
be one option per line).

What is your feedback on this? Other options could include sourcing
~/.eclipserc, I don't like that much (it would create yet another .* file in
the home directory). Plus this is probably something to set globally on the
system.

However, I was wondering if /etc/conf.d would be appropriate for an
application's settings. Most of the stuff there is either server related
(tomcat, apache etc...) or system related (alsa, clock, xdm...)

Thanks for the feedback, Elvanör

[-- Attachment #2: Type: text/html, Size: 1961 bytes --]

Re: [gentoo-java] Moving Eclipse-3.3 to tree

[Eivind Tagseth]

Jean-Noël Rivasseau wrote:
> 2) It would have a simpler configuration syntax (pure familiar Bash 
> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the 
> syntax in the eclipse.ini file is more obscure even for me - looks 
> like there should be one option per line).
>
> What is your feedback on this? Other options could include sourcing 
> ~/.eclipserc, I don't like that much (it would create yet another .* 
> file in the home directory). Plus this is probably something to set 
> globally on the system.
>
> However, I was wondering if /etc/conf.d would be appropriate for an 
> application's settings. Most of the stuff there is either server 
> related (tomcat, apache etc...) or system related (alsa, clock, xdm...)
>
How about an environment variable like ECLIPSE_MAX_MEMORY (or 
ECLIPSE_JAVA_OPTS) that's put in a file in /etc/profile.d?

This would let administrators set up good system defaults, while 
allowing users to override the settings in their own shell (command 
line, og .bashrc etc).


Eivind
-- 
gentoo-java@lists.gentoo.org mailing list

Re: [gentoo-java] Moving Eclipse-3.3 to tree

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

Eivind Tagseth kirjoitti:
> Jean-Noël Rivasseau wrote:
>> 2) It would have a simpler configuration syntax (pure familiar Bash 
>> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the 
>> syntax in the eclipse.ini file is more obscure even for me - looks 
>> like there should be one option per line).
>>
>> What is your feedback on this? Other options could include sourcing 
>> ~/.eclipserc, I don't like that much (it would create yet another .* 
>> file in the home directory). Plus this is probably something to set 
>> globally on the system.
>>
>> However, I was wondering if /etc/conf.d would be appropriate for an 
>> application's settings. Most of the stuff there is either server 
>> related (tomcat, apache etc...) or system related (alsa, clock, xdm...)
>>
> How about an environment variable like ECLIPSE_MAX_MEMORY (or 
> ECLIPSE_JAVA_OPTS) that's put in a file in /etc/profile.d?
> 
> This would let administrators set up good system defaults, while 
> allowing users to override the settings in their own shell (command 
> line, og .bashrc etc).
> 
> 
> Eivind

Environment variables would work but for example Debian has a strict 
policy against environment variable pollution. /etc/conf.d/ is not 
really meant for applications. I would suggest using .gentoo/eclipserc 
because that would avoid possible problems with upstream adding 
something like .eclipserc in the future.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

Re: [gentoo-java] Moving Eclipse-3.3 to tree

[Vlastimil Babka]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jean-Noël Rivasseau wrote:
> Hello all,
> 
> At this point all the dependencies for Eclipse were moved to main tree
> (they use the osgi eclass so they make suitable jars for Eclipse). So
> there is only now for Eclipse itself to be moved there.

Great!

> Just wanted to check that junit-4.4-r1, which was also moved to tree,
> does not trigger circular dependencies anymore (I checked on the
> bugzilla and it seems it is ok).

It really shouldn't now, I fixed all old junit depends to 3.8*. Also the
junit in tree depends on hamcrest-core and not whole hamcrest anymore so
it doesn't pull all the stuff it used to, and which triggered the problem.

> For information I plan to move it as 3.3.1.1 <http://3.3.1.1>, deleting
> the ebuilds in the experimental overlay except the ali_bush latest one
> (-r2).

Any reason to keep it? I doubt but ali_bush please respond. Is it the
timezones making communication hard? :)

> Finally I need advice on the following (which is the only thing left to
> be done on my agenda before putting Eclipse in tree):
> 
> 1) It looks a better Gentoo way (eg, users know about /etc/conf.d, they
> may not know about eclipse.ini)

Yeah but /etc/conf.d is really intended only for services, i.e.
/etc/init.d/*

> 2) It would have a simpler configuration syntax (pure familiar Bash
> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the
> syntax in the eclipse.ini file is more obscure even for me - looks like
> there should be one option per line).
> What is your feedback on this? Other options could include sourcing
> ~/.eclipserc, I don't like that much (it would create yet another .*
> file in the home directory). Plus this is probably something to set
> globally on the system.

The usual way for programs is /etc/eclipserc for system-wide and
~/.eclipserc for user overrides. If you could support this, great. Not
sure how much patching is involved to get rid of eclipse.ini and use
this way.

Caster

P.S. Any plans for future splitting eclipse into more pieces? :) We need
separate jface for example. There's already in java-experimental as
result of serkan's effort and his eclipse-rcp.eclass but I still have
doubts about this way of building from the src.zip which is only
intended for source discovery when writing code in eclipse...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHjy9BtbrAj05h3oQRAhU6AKCJvV9EP3UEYRZ1/TR3603g95I0wwCgjl9g
aGHl0+th8DH5U7nyvw89z1M=
=FeBh
-----END PGP SIGNATURE-----
-- 
gentoo-java@lists.gentoo.org mailing list