Thanks Pascal,
From wiki
Currently the processing is done breadth first, in that first all
the IUs are being fetched, then they are all installed and finally
configured. Is that too strict?
Yes I think that is too strict. For the general case (multiuser) it is too
restrictive to always get a configure with install, etc. The use case that
requires install only is a native service. It can install artifacts but it
can't configure for all users. The configure should occur when the user
starts the program. This likely also has implications for touchpoints since
there are touchpoint operations that should be done during install (like
global things) and operations that need to be performed on a user basis.
Pascal Rapicault
<Pascal_Rapicault
@ca.ibm.com> To
Sent by: Equinox development mailing list
equinox-dev-bounc <[email protected]>
[EMAIL PROTECTED] cc
Subject
08/16/2007 09:36 [equinox-dev] [prov] Thoughts on
AM the engine
Please respond to
Equinox
development
mailing list
<[EMAIL PROTECTED]
pse.org>
I have created an wiki page describing thoughts / questions about the
Engine. http://wiki.eclipse.org/Equinox_Provisioning_Engine
PaScaL
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: pic21410.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
