[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-tm-dev] TM Update Site is Confusing - Proposed Changes
|
Hi Kevin,
the TM update site is not really meant for initial
installation, but for
automatic updates. For initial
installation, better use the Europa
or Ganymede site -- this will resolve
dependency problems.
With respect to duplication of features, your confusion
might go away when
you untick the "Show latest version of a feature only" in
the Update Manager
Dialog. Then, each of the "TM and RSE {version}" categories
will be complete
in the sense that it lists all associated
features.
Regarding your specific proposals:
1. Have only RSE SDK and RSE Runtime.
That's done on the Europa and Ganymede sites. We cannot do
it on the TM site,
because the TM site is
also used by Update Manager itself for automatic
consumption. If just the
ftp feature, for instance, has been updated from 2.0
to
2.0.1 then users who do
"Check for Updates" do not want to install all of
the
RSE Runtime just to get
the newest FTP feature. That's why we need to
be
that granular on that
site.
Some of your confusion
might go away when you tick "Filter features
included
in other features on the
list" in your Update Manager Dialog.
2. Remove the duplication of Services/Remote CDT in 2.0.1 and 2.0.2.
Also the duplication of Discovery across 2.0, 2.0.1 and 2.0.2.
As mentioned above,
Update Manager does that for us. All features would
be
duplicated if you didn't
have "Show lates..." ticked. The ones you mention are
duplicated because they
were not changed between the 2.0x releases.
3. Move Discovery/Remote CDT and perhaps the Terminal to a
new update site called Extras. This will make it much easier for users who
just click the root node of the update site, as there won't be any dependency
problems.
Multiple update sites are a no-no IMHO because it makes
resolving dependencies
even harder. As I said, the TM site is meant for
automatic consumption while
the Europa / Ganymede site is for
users.
Whate we could do is in additoin to the site.xml file,
provide a site-simple.xml
file which only has a filtered list of components. I'm
torn, however, what that
filter should be like.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member