[eclipse-maintainers] Initial project questions

[Barry Hawkins]

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

Joerg Wendland wrote:
| Hi all,
| I am finally back to my Debian work.
[...]
Welcome back Joerg; I hope the thesis work turned out alright.

| I can't see any advantages or disadvantages in doing it either way.
|
| Besides that, here are some points I'd like to hear your opinion about:
|
|  - Do we need to maintain eclipse 2? There are still many commercial
|    tools based on it.
Most plugins that I use support 2.1.x and 3.x via separate downloads;
the only things I know that require 2.1.x are plugins for WSAD 5.x, with
which we have no dealings.
|  - Should we support packaged plugins? I think yes, but then how do we
|    handle plugins installed as Debian package? Should we disable their
|    updating through the update manager?
That's tough for me to say right now; the Firefox and Thunderbird
packaging teams must have faced the same question with the extensions
they package for Debian.  I would be concerned about trying to exert
more control over an installation's plugins than we are prepared to
support.  If someone wishes to update to a newer version without waiting
for it to appear in Debian packaging, then so be it; however, they
forfeit any promise that subsequent packaged plugin updates will work
properly.  If we attempt to control it, and other 3rd party plugins they
purchase somehow depend on ones we manage, then I would think we would
get a host of bug reports for issues beyond our control.
|  - Should we support multiple installed versions? One may want to have
|    both eclipse 3 and 3.1 installed.
I believe Eclipse is such that having the latest release version
available would be adequate; users who wish to go above or below that
could certainly perform a manual install.
|  - Should we build one big package or some small ones divided up by
|    functionality and usefulness as standalone packages:
|    o swt (which is already packaged)
|    o rcp (which one may want to use for applications)
|    o pde
|    o jdt (tomcat5 can use the jdt compiler for jsps)
My preference would be packages broken up much as you have outlined
above, but I will of course go with the majority here.

Regards,
- --
Barry Hawkins
All Things Computed
site: www.alltc.com
weblog: www.yepthatsme.com

Registered Linux User #368650
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB6/1I7bZ6kUftWZwRAtbZAKDOEgQ8aRJK8lBSpa9MkTJxpQv3BgCdHzV2
lxUUFyidmKaPLrn2OJstnws=
=wLUC
-----END PGP SIGNATURE-----