Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-tm-dev] Getting rid of RSE SDK from Ganymede?

Correct, they would do what you say.
Or, get the RSE-SDK.zip from our download site.
 
IMHO, SDK Users are the integrators and extenders of RSE
(And not the users), and thus in most cases would use the
download rather than the update site.
 
But if they want to use the update site, yes, they get Platform,
then install RSE from the Ganymede site, then get RSE SDK
from the The TM Update Site (which gets auto-configured
as a known Repository once TM-Runtime is installed).
 
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
 
 


From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of David Dykstal
Sent: Friday, June 06, 2008 8:55 PM
To: Target Management developer discussions
Subject: Re: [dsdp-tm-dev] Getting rid of RSE SDK from Ganymede?
Importance: High

When you say "remove from Ganymede" you mean remove from the packages we provide to the Ganymede update site, correct? Thus, a user desiring the SDK would need to

1) get a platform (which includes the def of the Ganymede update site)
2) update to get the RSE runtime (which includes the def of the project update site)
3) update to get the SDK

This is OK with me, but am I understanding it correctly?

Since the SDK is available on the project site, I don't think it affect IBM's consumption of it. I'm pretty sure our scripts pull it directly off the project site.

-- Dave

On Jun 6, 2008, at 1:44 PM, Oberhuber, Martin wrote:

Dear TM Committers and Community,
 
quick round call: Should we remove the RSE SDK from Ganymede?
 
Ganymede is really mostly about tooling for users, so they'd typically
rather have the RSE Runtime and avoid the added overhead for
downloading sources and developer docs. (SDK == Runtime + Sources
+ ISV Docs, as a reminder). Only few projects ship their SDK's on
Ganymede along with the Runtime.
 
On the other hand, having sources available is of course helpful
for diagnosing issues oneself (debugging, self hosting). But in my
opinion, a person who'd want to do that can very easily get the
SDK from our TM Site after the initial Ganymede install, if desired.
 
In my opinion, Ganymede should be the first-time-start package
for users (without SDK), and it should not hurt to select all of it.
 
Any other opinions?
 
Note that we already have some features that we do not ship on
Ganymede but on our project update site only: RSE-examples,
RSE-wince, RSE-unittests. On Ganymede, we'd then have
  • RSE-Runtime
  • Remotecdt
  • Discovery
  • RSE-Useractions
  • RSE-terminals
  • TM-terminal
Is that too much granularity? Should we define a special "Ganymede"
feature that packs Useractions into the Runtime? Or pack the User
actions right into the Runtime per default already? Or, have an
"RSE Ganymede Runtime" that == RSE-Runtime + RSE-Userations +RSE-Terminals ?
 
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
 
 
_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev


Back to the top