[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Update on eclipse 3.7



On 2011-08-05 13:40, Niels Thykier wrote:
> Hi
> 

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.
> 

Time for an update, I guess.  The attentive reader will have noticed
eclipse 3.7 (3.7~exp-1) got upload to experimental.  Obviously this
means that...

>   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.
> 

this is fixed.

>   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 is has not been b0rked since it was fixed. :P

>   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].
> 

this is out-dated; use the one from the package (also in git).

>   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.
> 

as far as I can tell, this has been fixed.  But if something sneaked
past me, let me know.

>   Five, we need some upstream tarballs (my builds were done with -b).
> But we generally need to deal with item four first.
> 

this has been fixed.

>   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.
> 

the upstream and master branches on the git has been updated to 3.7.


Okay, end of updates.  Time for the second round of things that needs to
be checked/fixed.  These items stalls uploading 3.7 to sid.

 * Test the binaries - so far I only know it builds on amd64.  It
   *probably* works, but feel free to take it for a spin.

 * Check that other eclipse packages still build.  Particularly, check
   the "pdebuild" script in eclipse-pde was generated correctly.
   - feel free to file bugs accordingly.
   - eclipse-cdt will probably need a new upstream version.

 * Check up on some of the lintian warnings.  There was at least one
   warning about a symlink being absolute.  I could not figure out why
   dh_link did not fix it.

 * All the other issues I forgot about.  Yes, I expect you to know what
   I forgot! :P

> 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).
> 
> [...]
> 
> Getting some working sources:
> 
>  [...]
> 

reduced to:
 $ git clone git://git.debian.org/git/pkg-java/eclipse.git
 $ # wget tarballs from $local_mirror when they arrive

> Help is much appreciated and questions are welcome, happy hacking.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Particularly that still holds! :)

~Niels


Reply to: