Hi Markus, Le 03/09/2018 à 14:48, Markus Koschany a écrit :
> I think this could have been better communicated. I was the one who > split libequinox-osgi-java off from Eclipse. Why can't we just use the > existing package and update it accordingly? In any case giving a reason > for a package takeover by another package even for team-maintained > packages seems appropriate to me. A bug report would have been ideal for > this sort of discussion. Sorry if this wasn't clear but I did mention taking over libequinox-osgi-java with src:equinox-framework in July when I exposed my plan to package the Eclipse dependencies required by AspectJ [1] on the debian-java mailing list. I didn't receive any feedback on this point and I didn't expect it would be controversial. Don't get me wrong, this is definitely not a disapprobation of your work and I apologize if it looks like it. Your move to split libequinox-osgi-java from src:eclipse was the right decision to move things forward and I fully support it. But after having packaged a large set of Eclipse modules the libequinox-osgi-java package now appears at odds with the newly introduced packages (Maven Central as upstream vs Eclipse Git repository, different naming convention, different build system, no upstream version tracking). That's why I think it's more consistent to replace libequinox-osgi-java now. Emmanuel Bourg [1] https://lists.debian.org/debian-java/2018/07/msg00020.html
