Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Ganymede M5 problems


the disadvantage of SDKs on Ganymede is that folks who
just select all to grab "all of Ganymede" (who is that,
actually, except us crazy people testing that stuff?)
get more than they typically want or need, thus wasting

In the GMF case, I'm inclined to propose adding the
Eclipse SDK feature to Ganymede to help resolving the
issue (and be curious how much extra space the source
plugins would be... Kim do you have an idea?)

But before we start breaking our heads over current 
update manager issues and limitations, I'm wondering
what the P2 Story will be for Ganymede?

I suppose that we will be using P2 in the end? Will it
offer any features to help ease the SDK vs. Runtime 
dilemma? Like multiple levels of Categories, for instance?

Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx 
> [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On 
> Behalf Of Markus Knauer
> Sent: Donnerstag, 21. Februar 2008 14:36
> To: Cross project issues
> Subject: Re: [cross-project-issues-dev] Ganymede M5 problems
> Putting a SDK on the Ganymede update site is a 'could do' 
> according to 
> When doing an EPP package build, we are currently adding the 
> Eclipse Platform 
> update site manually and pull the SDK feature from there. (I 
> think it was me 
> who complained about those SDK dependencies some time ago, 
> but in the end i 
> do not have a strong opinion)
> Markus

Back to the top