Re: [platform-update-dev] Link files

[klicnik@xxxxxxxxxx]

The link support is in the builds, basically as described in the spec, with the following exceptions (spec needs to be updated):

(1) the location of the "links" directory is computed relative to the location of the platform configuration file. At this point the full configuration handling is not completed (ie. full support for the new -configuration argument), so by default, the configuration file is in <eclipse>/install/.metadata/ .... so <eclipse>/install/.metadata/links/ would be the default directory (the spec is missing the .metadata level)
(2) we will allow the native install to be optionally updatable. This is specified in the actual link entry. The spec defines the entry as
path=install-path[,install-path]* 
where each install-path entry is a platform file path to another install directory (the parent directory of "plugins/" in the native tree). The code actually allows each path entry to be prefixed by "r" or "rw" to indicate if the directory is updateable by the Eclipse update functions (default is "r" ... not updateable).

For example:
path=c:\\root1\\,rw d:\\temp\\,r e:\\shared\\
results in c: and e: paths to be read-only, and d: r/w

Remember the file is a Java properties file ... so on Win must escape the path separators. The actual link files can be named anything you want ... the spec suggests plugin-id-like naming convention to minimize chance of conflict. The startup code processes all files found in links/

Please respond to platform-update-dev@xxxxxxxxxxx

Sent by:        platform-update-dev-admin@xxxxxxxxxxx

To:        platform-update-dev@xxxxxxxxxxx
cc:        
Subject:        Re: [platform-update-dev] Link files


Peter,

I know that this is in the section about native install/uninstall, and
that these items can not be updated.  As all the plugins I currently
have are not managed by the update manager but rather manually
installed this seems very much the right thing to do until each
of the plugins I am using is set up so that the update manager
can handle them.

This however still leaves the question, what is the file format and are
they implemented?

David

On Wednesday 13 February 2002 15:55, you wrote:
> I don't know if they are implemented or not yet but if you use these link
> files then the update manager can't be used to update those plugins pointed
> to by the link files.
> WSAD for instance can't and won't be using them if at all possible.
>
> Thanks,
> _____________________________________
> Peter Manahan
> WSAD Linux Port Team
> VisualAge for Java Release Lead
> manahan@xxxxxxxxxx
> _____________________________________
>
>
>
>                     David Goodenough
>                     <david.goodenough@btconnect       To:    
> platform-update-dev@xxxxxxxxxxx .com>                             cc:
>                     Sent by:                          Subject:    
> [platform-update-dev] Link files platform-update-dev-admin@e
>                     clipse.org
>
>
>                     02/13/2002 07:16 AM
>                     Please respond to
>                     platform-update-dev
>
>
>
>
>
> In the design document for install/update in the Changes for R2.0
> section, there is a bullet point "using native install/uninstall".
>
> At the very end of this it says:-
>
> The shared Eclipse is make aware of the product-specific location via
> and installed "link file".
>
> 1) Is there a definition of such link files, their format, their naming
> conventions, and their location?
>
> 2) Is this implementated yet?
>
> Regards
>
> David
> _______________________________________________
> platform-update-dev mailing list
> platform-update-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-update-dev
>
>
>
>
> _______________________________________________
> platform-update-dev mailing list
> platform-update-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-update-dev
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev