On 2011-08-05 13:40, Niels Thykier wrote: > Hi > > This email is BCC'ed to #631061 and #631382; please consider following > up to d-java@l.d.o as it makes coordination easier. > > I have managed to successfully compile eclipse 3.7 using part of the > debian packaging I just pushed to the git repository[1]. There are at > least six issues atm. > > First off, my build did not use any of the patches in d/patches. > Hopefully it means most of them are redundant, but more likely it means > something will break. > Note: Some of these patches may require > eclipse-build-generatedScripts.tar.bz2 to be updated. If the build > fails horribly after applying a refreshed patch due to "missing classes" > or "cannot find package", you probably hit one of those cases. > > Secondly, upstream commented out a couple of architecture support > patches in the upstream build.xml. As I recall the argument was they > did not apply cleanly, so they need to be refreshed as well. >
This one has been applied upstream[1]. [1] http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/commit/?id=fff4c2c133d9fb2241533ae09f9a1add84844e84 > Third, the "eclipse-build-generatedScripts.tar.bz2" in the upstream > git does not work for us. I have deviced a functional version for > Debian at [2]. > > Four, there are some zip/pre-compiled crap in the upstream sources we > need to get removed. Most of it will probably be fixed with refreshing > the Debian patches and just removing the left overs, but we need to > double check this. > > Five, we need some upstream tarballs (my builds were done with -b). > But we generally need to deal with item four first. > > Six, the upstream branch (merged into master as well) is some older > version of eclipse (I think 3.6.2, but I could be wrong). This is > trivially fixable once we got some clean tarballs from item five. > > If you would like to help with any of those, feel free to claim a task > and work on it. Alternatively, there are some upstream bugs that we > could really benefit from, if they were fixed (see [3] for more info). > > Caveat: If you work on any of these tasks, you must be ready to send a > patch upstream. Upstream only accepts patches from the original author > and only via their BTS. It is a part of their "IP Cleanness" strategy > and they do not make exceptions! > > > Getting some working sources: > > $ # Fetch eclipse-3.7.0-src.tar.bz2 from > http://download.eclipse.org/technology/linuxtools/eclipse-build/3.7.x_Indigo/ > $ git clone git://anonscm.debian.org/pkg-java/eclipse.git > $ tar xjf eclipse-3.7.0-src.tar.bz2 > $ git clone \ > http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/ > e-b > $ cd e-b/eclipse-build > $ ln -s ../eclipse-build-config . > $ ln -s ../eclipse-build-feature . > $ mv ../../eclipse-3.7.0-src eclipse > $ cp -r ../../eclipse/debian/ . I forgot to add two lines here: $ # open nonosgidependencies.properties and comment out # ant-testuitl.jar line $ wget http://people.debian.org/~nthykier/eclipse-build-generatedScripts.tar.bz2 > $ # install B-D from d/control and dpkg-buildpackage -us -uc -b > # should work up to dh_install that will fail due to a missing > # manpage carried on one of our patches. > > Help is much appreciated and questions are welcome, happy hacking. > ~Niels > > [1] http://git.debian.org/?p=pkg-java/eclipse.git;a=summary > master branch > > [2] > http://people.debian.org/~nthykier/eclipse-build-generatedScripts.tar.bz2 > > [3] Upstream bugs that needs fixing (eclipse 3.7): > - Better support for shared read-only installs (#587657) > - https://bugs.eclipse.org/bugs/show_bug.cgi?id=351485 > - This bug is really a pain; cost two t-p-u for Squeeze > - Default update site list blank in shared install > - https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133 > - patches welcome (see comment #25) > > ~Niels -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3bff19.6020...@thykier.net
