Re: [linuxtools-dev] Unified launcher for remote profiling?

[Aleksandar Kurtakov <akurtako@xxxxxxxxxx>]

----- Original Message -----
> From: "Daniel H Barboza" <danielhb@xxxxxxxxxx>
> To: "Linux Tools developer discussions" <linuxtools-dev@xxxxxxxxxxx>
> Sent: Friday, November 23, 2012 3:31:38 PM
> Subject: Re: [linuxtools-dev] Unified launcher for remote profiling?
> 
> 
> What I've got from this discussion so far is that the remote
> infrastructure in Linuxtools is lacking. There are no standard in
> plug-in names, unit testing can be improved and so on. I agree with
> that, we can do better.
> 
> On the other hand, right now we have an unified local launcher that
> is
> user friendly and polished, providing a better experience for the
> user.
> This makes the remote capability looks deprecated and I',m afraid
> that
> many users will "neglect" the remote support at all.

This is not something I'm happy with but with the current amount of energy spend on the projects it was better to have a "user friendly and polished, providing a better experience for the user" local launchers than waiting for the bright future when we will eventually have remote to the same state.

> 
> My point is that the user won't notice if there's any unit test
> missing
> or any lack of standardization of the remote framework, but he'll
> sure
> notice that there is no unified remote launcher. 

While I agree about the user experience topic you mentioned there is something else that is equally important - long term supportability. It doesn't matter if you please users now using ten different approaches because we don't have the resources to support that and if we don't unify remote launchers too something will always be broken - with all the different approaches used users don't know what and how to use nor we do. Creating stable base for 2.0 (Kepler release) for remote launchers would be the best.

> That said, I'll
> start
> working on this unified remote launcher and cleaning up the remote
> infrastructure on the process. Of course that this cleaning up will
> continue after the unification, but at least we'll offer both remote
> and
> local unified launchers to the user to play with.

I'm more than happy to hear that. Note that there are plans for further integration in CDT (https://bugs.eclipse.org/bugs/show_bug.cgi?id=391608) which Jeff is looking at so trying to hook remote in CDT will be needed or it will be one step behind once this lands again.

Alexander Kurtakov
Red Hat Eclipse team