|Re: [dsdp-pmc] RE: [cdt-dev] CDT and Galileo|
Hi Doug,In my opinion, the biggest benefit of the coordinated update site in the past was that dependencies got automatically resolved.The "two-step-installation" scenario that you propose for "optional add-ons" to CDT is flawed in several ways:
- In the Remote CDT case, I need to think about installing RSE in the first step BEFORE I get the remote launcher in the 2nd step. Who would ever think about this?
- Optional pieces are hard to find. As of Galileo M7, no additional repositories are added when I install all of Galileo. I won't know the URL of the CDT repository. This may be a current p2 bug, but on the other hand, if all contributing project's repositories were added, how would I find the CDT one?
- DD-DSF and RemoteCDT have been on Ganymede. Not having them in Galileo is a regression. Clients may just expect finding it there.While I agree that the Galileo site is going to become large, I cannot see how adding the following would lead to any more confusion:
- Collaboration > Mylyn Bridge: C/C++ Development
- Device Development > Eclipse C/C++ DSF gdb Integration
- Device Development > Eclipse C/C++ Memory View Enhancements
- Device Development > Eclipse C/C++ Remote Launch
I took the freedom of remaming some of the features (memory view, DSF, Remote Launch) for the sake of being more end-user consumable on a coordinated site such as Galileo. But given that p2 finally sorts contributions alphabetically, I would really appreciate seeing these contributions on Galileo.
I do believe that having these on Galileo is important for the whole DSDP message, thus I'm CC'ing the DSDP PMC.
And BTW, as I've mentioned before I'm in favor of re-introducing the Ganymede category name of "Remote Access and Device Development" rather than just Device Development as it's today.Cheers,--Martin Oberhuber, Senior Member of Technical Staff, Wind RiverTarget Management Project Lead, DSDP PMC Member
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Montag, 11. Mai 2009 16:19Subject: Re: [cdt-dev] CDT and Galileo
To: CDT General developers list.Hi Martin. We're treat the Galileo repository as a spring board to the C/C++ IDE. All other features for the CDT, of which there are many, are available in the CDT repository. We discussed removing remoteCDT from Galileo, and it was a tough decision, but we've decided to treat it under the same rules as the other CDT features. The Galileo repo is going to be a disaster. There are way too many projects contributing to it and I don't want to add to the mess.
At the end of the day, the EPP packages should be the main vehicle where the user community gets their Eclipse plugins. We need an Embedded Development IDE EPP package and that's something I figure would come out of the DSDP Packaging project if it ever gets off the ground.
On Mon, May 11, 2009 at 9:14 AM, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
PS DSF is also missing in Galileo.DSF and RemoteCDT missing are regressions compared to Ganymede, where they have been in...Cheers,--Martin Oberhuber, Senior Member of Technical Staff, Wind RiverTarget Management Project Lead, DSDP PMC Member
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Montag, 11. Mai 2009 15:10
To: CDT General developers list.
Subject: [cdt-dev] CDT and GalileoDear CDT gurus,I just tried to get "All of Galileo M7" and noticed some missing from CDT:
- Mylyn CDT connector missing in Galileo -- should be in "Collaboration" category
- RemoteCDT Launcher missing in Galileo -- should be in "Device Development" categoryOr are these deliberately not in Galileo?Thanks,--Martin Oberhuber, Senior Member of Technical Staff, Wind RiverTarget Management Project Lead, DSDP PMC Member
cdt-dev mailing list
dsdp-pmc mailing list
Back to the top