Re: [linuxtools-dev] Updating from nightly builds

[Andrew Overholt <overholt@xxxxxxxxxx>]

* Michel Dagenais <michel.dagenais@xxxxxxxxxx> [2010-07-19 10:04]:
> 
> > Do you have the main Helios repository enabled?  PDE is required for
> > the "RPM Stubby" feature and it looks like it can't be found in any of
> > your enabled repositories.
> 
> Like many Linux tools users (or candidate users), I have a Linux/GNU
> background (configure; make; make install). You may want to insure
> that you have a quick document to tell such people how to get started:

Yes, some sort of getting started documentation would be good.  I've
opened a bug regarding this in case we have any people looking for a way
to contribute:

  320267: Create "Getting Started" user documentation
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=320267

> - which version to install from the helios download

By this do you mean which package to install from here:

  http://www.eclipse.org/downloads/

?  The problem is that there are multiple choices.  One can install any
of them, really, and then install the Linux Tools components on top.

> - how to add/update and remove components systemwide

In Fedora, we use the dropins mechanism for this.  It's fragile and the
p2 developers would like to get rid of it so we are planning to
investigate alternative methods.  In the meantime, this may be of
interest to you:

  http://wiki.eclipse.org/Equinox_p2_Shared_Install

> Cannot complete the install because of a conflicting dependency.

It looks like you installed something as the root user and then tried to
update it as a non-root user.  If you were to try everything as a
regular user, it should work.

It would help me to help you if I understood your requirements and
expectations.  What exactly are you trying to accomplish?  I know it's
foreign to you as a *nix user, but the most common way of "installing"
Eclipse is to download something and extract it in a user-writable
location.  The "installation" directory is then managed by p2, the
Eclipse update system, with files being added and removed as
installations or updates are performed.  Care must be taken with
multi-user installations.  Since it appears that, as root, you installed
an EPP package (the tarball you downloaded from eclipse.org including
all the Linux Tools stuff plus the CDT, etc.) non-root users won't be
able to upgrade any of the "stuff" in there.  A perhaps more common
example would be Firefox.  A system administrator may put Firefox into a
location that is read-only for non-root users but if he or she put
Firefox plugins into that same location, would he or she expect non-root
users to be able to update those?  I don't know if Firefox allows
non-root users to "mask" system-installed components in this way but
Eclipse does not (well, one could perhaps do it but it's not
straightforward out of the box).

If one extracts the archive as a root user (thus making it read-only for
non-root users), the update sites that were present in that read-only
location are not persisted to the non-root user's "installation".  This
is bug #249133 [1].  I think this is the root of your problem.  I don't
recommend it, but had you done the following, things would probably have
worked as you expected:

- as root, extract the Linux Tools EPP package to /opt/eclipse
- as a regular user, run /opt/eclipse/eclipse
- as a regular user, add the main Helios update site since it was not
  persisted into the user's installation
- install more of the Linux Tools components than what were included in the
  EPP package

>   Software being installed: Valgrind Tools Integration (Incubation) 0.4.0.201007141806 (org.eclipse.linuxtools.valgrind.feature.group 0.4.0.201007141806)

It looks like you might have our nightly Helios update site
(updates-nightly-helios) enabled.  Was this intentional?

Andrew

[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133