[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] [prov] Comments on wiki "Equinox p2 Shared Install Plan"
- From: James D Miles <jdmiles@xxxxxxxxxx>
- Date: Mon, 17 Dec 2007 11:36:05 -0600
- Delivered-to: firstname.lastname@example.org
bundles.txt stored in user home.
YES. I would change that to stored in users workspace or preferable user's configuration space.
If bundles.txt is missing from the user's workspace then it needs to be populated with the shared bundles.txt.
This should contain the minimum plugins required for provisioning the remainder. If it is not missing and the minimal shared bundles.txt is newer then it should be replaced. The assumption is that it is always forward/backward compatible. This replacability takes care of fixes to the core provisioning functionality. It would be nice if the bundles.txt is structured to accommodate replacing the core definitions easily.
If you want to populate the user's bundle.txt with sdk in shared install then in can be driven as a root IU or profile. However this is a policy decision and should not be hard-wired as always happening. The act of provisioning the bundles also allows for the unfolding/customizing of additional artifacts related to specific bundles. An example of additional work would be creating user ICONs, setting environmental variables.
What we are really talking about is running only a configuration phase to get the user's bundle.txt up to the latest. The phases collect, and install are not wanted.
Materialize profile from running bundles.txt
I am suggesting it is better to materialize bundles.txt from the profile.