[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] Equinox initializer
|
This topic is testing my memory. Did we ever build the equinox initializer? I don't think so. At any rate I am afraid the initializer code did not migrate over to the new git repositories (at least I am not able to locate it) and it is not being built in the current builds. Is it time to bring this bundle into a git repo and start building it? If so I suggest just placing it in the rt.equinox.bundles repo.
That issue aside: for your question. Do you always use -clean to startup the user's instance of eclipse? If so I am wondering if it is a sorting issue in the order that p2 uses when installing bundles. In theory p2 should be installing bundles in a consistent order when starting from a clean cache. If not then the bundle IDs will change when you run with -clean for the users instance of eclipse.
Tom
Krzysztof Daniel ---01/03/2013 05:33:58 AM---Hey all, In Fedora, we used to use Eclipse Equinox initializer to extract all
From: Krzysztof Daniel <kdaniel@xxxxxxxxxx>
To: equinox-dev@xxxxxxxxxxx,
Date: 01/03/2013 05:33 AM
Subject: [equinox-dev] Equinox initializer
Sent by: equinox-dev-bounces@xxxxxxxxxxx
Hey all,
In Fedora, we used to use Eclipse Equinox initializer to extract all
*.so files from the installation before the Eclipse was actually
installed via rpm. This had some advantages:
* Reduced disk usage for people with tight user.homes or using nfs.
* Ability to run Eclipse when home is mounted as noexec (for security
purposes).
This is no longer the case, because I can find those libraries
find /usr/lib64/eclipse/configuration -name *.so
/usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/35/1/.cp/os/linux/x86_64/libunixfile_1_0_0.so
/usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/38/1/.cp/libgnomeproxy-1.0.0.so
/usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/153/1/.cp/libswt-glx-gtk-4235.so
[...]
in my home:
find ~/.eclipse -name *.so
~/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.osgi/bundles/81/1/.cp/os/linux/x86_64/libspawner.so
~/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.osgi/bundles/143/1/.cp/os/linux/x86_64/libunixfile_1_0_0.so
~/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.osgi/bundles/774/1/.cp/libswt-webkit-gtk-4235.so
[...]
The first thing that I've noticed is that bundle numbers had changed
(and they do actually change if I call eclipse -clean, although not
always).
What may be the cause of this behavior? How to get back to the good ol'
behavior where *.so files were not duplicated?
Interesting documentation is:
http://wiki.eclipse.org/EquinoxInitializer
Bug 90535 - .so files installed in a strange location
https://bugs.eclipse.org/bugs/show_bug.cgi?id=90535
Best regards,
Chris
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
