Hello :)
Eclipse is its own ecosystem, with all sorts of conventions and
peculiarities. In addition, we have several applications each using
only particular
parts of eclipse e.g., just OSGi/equinox, just RCP, just SWT etc.
So, IMHO there is lots of room for incompatibilities and pain, like
putting stuff (like .so libraries) in a place where they are hard to
find by another package etc.
Does that mean we need an eclipse policy following debian tradition?
Fedora already has some guidelines that cover
* Naming of plugins / applications that just
depend on eclipse
* Installation locations for core, native
libraries, and plugins with and without native code
* Other misc stuff
You can find those guidelines in
http://fedoraproject.org/wiki/Packaging/EclipsePlugins
If a debian eclipse policy is needed, what should it contain?
Cheers,
Pantelis
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
