Re: [platform-update-dev] Install / Update Reconciliation

["Dorian Birsan" <birsan@xxxxxxxxxx>]

Some comments below (enclosed by <db></db>)

-Dorian

"bhavin  raichura" <bhavin_r@xxxxxxxxxxxxxx> Sent by: platform-update-dev-admin@xxxxxxxxxxx 08/05/2003 11:17 PM Please respond to platform-update-dev

To:        platform-update-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-update-dev] Install / Update Reconciliation

Hi,

What is the exact mechanism for Reconciliation Install / Update in 
case of:

    1. Updating existing installed features / plugins
    2. New Available Features / Plugins

How does the logic works ? What are the minimum things needs to be 
present on both side (Client / Updatesite) to make it work ..?

<db>
Your question is a bit too broad, so here is a short
answer:

There is a notion of a installation configurations,
which are really snapshots of collections of features after certain installation
actions. 
So, when eclipse starts, a current configuration is
created, based on what features are installed.
After some features are updated or after new features
are installed, another configuration is created and set current.
Update sites contain newer version of existing features
or new features. These remote feature have certain constraints (feature
dependencies, environment requirements, etc.) that must be satisfied before
installing them in the current configuration.
For example, if the update site contains feature A
1.0.0, which references plugins P 1.0.0 and Q 1.0.0 (both plugins being
present on the update site), and has a dependency on feature B 1.0.2, then,
if the current configuration contains feature B 1.0.2 then A 1.0.0 can
be installed. The feature and the two plugins will be downloaded and installed
in the current configuration.
<db>

I have seen some xml files such as V2LocalSite.xml, V2Config*.xml 
in platform.cfg.metadata folder under workspace....what it 
means...? 

<db>
These are internal files, you should not be worried
about them.
</db>

Is it caching the update site ? How will it check
for 
the updatesites for new updates / new installs on next startup / 
schedule ? 

<db>
In the latest integration builds, the sites are not
cached, but their timestamp is compared to that on the server and only
when there is a different timestamp the lookup for updates continues.
</db>

When I change the UpdateSite URL in features.xml of
org.eclipse.platform_3.0.0 to my tomcat server it puts a new entry 
in install-log file and probably creates one more V2Config*.xml 
file...

<db>
Yes, you have made a configuration change, that is
detected and the internal state is updated to reflect this change.
</db>

Thanks in advance.
Bhavin Raichura


___________________________________________________
Download the hottest & happening ringtones here!
OR SMS: Top tone to 7333
Click here now: 
http://sms.rediff.com/cgi-bin/ringtone/ringhome.pl


_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev