Re: [linuxtools-dev] Problems with eclipse-build-5791c48513b4207ab1eec1e

[Alexander Kurtakov <akurtako@xxxxxxxxxx>]

On 16:20:57 Friday 22 July 2011 Thomas Gellekum wrote:
> Moin,
> 
> for the FreeBSD port of Eclipse-3.7.0, we're using the files available
> from
Welcome FreeBSD it's nice to see the list growing :)

> http://download.eclipse.org/technology/linuxtools/eclipse-build/3.7.x_Indig
> o/. I have a few questions regarding problems I encountered when updating
> the port. Please redirect me, if this is not the appropriate list.
> 
> Basically, we're running "ant -Dprefix=/usr/local; ant
> -Dprefix=/usr/local install" and expect an installation in
> /usr/local/lib/eclipse (system wide location, not writable by users).

Well, in Fedora we do smth slightly different:
ant provision.cvs
ant -DdestDir=$RPM_BUILD_ROOT -Dprefix=/usr -Dmultilib=true installSDKinDropins

It would be good if someone makes provision.cvs the default target, removes 
install and renames installSDKinDropins to simply install. This is the way to 
go and I doubt anyone is testing what you're using hence the problems. 

> I
> have done this on FreeBSD 8-stable (64bit) and Fedora 14 (32 bit). Minor
> problems I've seen on both systems:
> 
> 1. The "label" property should be "3.7.0", or the
> eclipse-3.7.0-src.tar.bz2 needs to be redone to include the buildId.
This has been fixed in master. See 
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-
build.git/commit/?id=627b5f8702211471ab373407d82065b0889dfa41

> 
> 2. The "provision.sdk" target needs to install the
> org.eclipse.equinox.initializer plugin, or the "install" step will fail.
Look at my first sentence. We managed to accumulate some crap that needs to be 
deleted. I don't envision eclipse-build supporting two types of builds with 
and without moving jdt and pde in dropins. We simply don't have the manpower 
for it. 
The only installation/build layout I plan to support is with jdt and pde in 
dropins because this matches distros instalations more. Others may want to 
support the layout of Classic Eclipse but if someone plans to do that he/she 
should step in otherwise this parts will be removed.

> 
> 3. The invocation of sed(1) fails in "install", because ${destDir} and
> ${destDirWithUnderscores} are empty.
> 
> I have patches for these, prepared by hand, but I guess you'll want them
> generated from git?

I guess this would work once you move to the supported targets. Look at Fedora 
spec for details 
http://pkgs.fedoraproject.org/gitweb/?p=eclipse.git;a=blob;f=eclipse.spec;h=53840e04b526a116f5ce8aca3d91602b70bcbd01;hb=ed463deb3bfa432d95c596826db8906aa662cf3e

> 
> The forth problem is actually bothering me most; it's not a
> show-stopper, but still annoying and a regression with respect to 3.6:
> 
> 4. The installed eclipse behaves differently from a downloaded
> distribution (Eclipse SDK, available from
> http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/inde
> x.php, installed into a system wide location, not writable by users) when
> it comes to installing new software.
> 
> Scenario: start Eclipse, Help->Install New Software..., work with: <EGit
> update site>, select features, install, restart. Using the installation
> built from src as described above, the restarted Eclipse does not
> recognize the new EGit and JGit features; they will only show up in the
> installation history. The files are in the user's $HOME/.eclipse
> directory, and they are listed in artifacts.xml. I see this behavior on
> both FreeBSD and Fedora.
> 
> The same scenario using the pre-built Eclipse SDK download works fine.
> The same scenario works fine with Eclipse-3.6.2 on FreeBSD, using the
> eclipse-build downloads in
> http://download.eclipse.org/technology/linuxtools/eclipse-build/3.6.x_Helio
> s/.
> 
> I've compared configuration files of the different installations, but
> nothing really jumps out. I've tried debugging the p2 machinations by
> setting the
> 
> org.eclipse.equinox.p2.core/debug=true
> org.eclipse.equinox.p2.core/reconciler=true
> 
> options; the output shows that some file visits are differently ordered,
> but that could be just a threading artifact and mean nothing.
> 
> Can anyone shed some light on this? What's the release build doing
> differently than eclipse-build? Where would I look next (knowing nothing
> about the p2 internals)?
Installing from update sites with fedora builds works for me. Please build 
with the targets I pointed you to and report back.

Good luck,
Alex

> 
> Any help is appreciated.
> 
> Best regards,
> 
> tg
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev