Re: [linuxtools-dev] Changing the PATH for execution of linuxtools comma

[Andrew Overholt <overholt@xxxxxxxxxx>]

* Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> [2011-09-30 15:10]:
> > -----Original Message-----
> > From: linuxtools-dev-bounces@xxxxxxxxxxx 
> > [mailto:linuxtools-dev-bounces@xxxxxxxxxxx] On Behalf Of 
> > Andrew Overholt
> > Sent: Friday, September 30, 2011 3:03 PM
> > To: Linux Tools developer discussions
> > Subject: Re: [linuxtools-dev] Changing the PATH for execution 
> > of linuxtools commands
> > 
> > * Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> [2011-09-30 14:44]:
> > > [...] we have a UI box in the launch configuration dialog that
> > > defaults to 'gdb' but that the user can change to the location
> > > she needs e.g., /home/user/bin/myOlderGDB
> > > 
> > > I'm curious to know if this is something you considered?
> > 
> > I'm not particularly involved in this PATH effort so take my comments
> > with a grain of salt but I personally dislike this type of unnecessary
> > UI cruft.  I would much prefer to support this case of vendor 
> > tool SDKs
> > through an extension point or some other non-UI mechanism if possible.
> 
> Yes, for vendor it makes sense to hide it under the hood, but I believe
> this issue was a user problem, where the user herself wanted to choose
> different versions at different times.

Is this that common?  I can see how it would be for gdb where there is
lots of progress and people have multiple versions installed.  But for
relatively standard tools where the plugin integration isn't changing
too much, I'd rather take minimalist approach.  The Eclipse preferences
situation is out of hand and so is the CDT project settings UI (IMHO).

Andrew