Provisioning Multi User Install Concerns2

• Upstream SDK will be delivered as a zip and include:
  • a metadata repository
  • an artifact repository
  • a plugins folder
  • a profile
    • pre-provisioned with contents of SDK
  • a configuration directory
    • bundles.txt

• Idea: provision at install time in %post
  • all the bits (MR, AR, jars) are dropped onto disk
  •  %post script does the actual provisioning operation of adding the bits to

 the system-wide profile

• Other idea: ship a profile with each package and have a system*wide one that

"includes" all of them

• • sort of like gcj.db

• Profile inheritance is important
  • ideally there'd be some sort of system-wide profile that will only (except

 in rare circumstances) be modified by RPM installations and uninstallations

• • then each user could over-ride the system-wide profile with their own

 installations.  Users should also be able to selectively disable/enable
 system-wide stuff.

• Issues to watch out for
  • plugins that do odd stuff in the provisioning install/post hook
    • perhaps we should have a policy that doesn't allow stuff like that?
    • ideally this would be done in at RPM build time