Both for installation and for runtime configuration, it is useful to have "grouping" products, which only have a .table file listing other products to install or to setup. The point is that several subsystems do not depend on each other, but we often want to handle them together.

Examples might help; I'll just list groups for the top-level actors; many important products get picked up automatically from those (tron_actorcore, ics_actorkeys, etc), and I'll leave the GUI parts off the lists.

• ics_CORE
  • tron_tron
  • ics_archiver
  • ics_alertsActor
  • ics_gen2Actor
• ics_SM:
  • ics_enuActor
  • ics_ccdActor
  • ics_xcuActor
  • ics_hxActor
• ics_FPS:
  • ics_mcsActor
  • ics_fpsActor
  • ics_mpsActor
  • ics_mebActor

And I'll suggest a top-level product, for everything:

• ics_PFS:
  • ics_CORE
  • ics_SM
  • ics_FPS

If you do not have these, it can be annoying and error-prone to do the equivalent of, say, eups distrib install ics_SM 2018-03-01 or setup ics_SM.

I don't feel strongly about the names, but would prefer them to be easy to type. The details of what go in the .table files can be dealt with later – I can easily see having the products listed in ics_CORE above being included in ics_SM or ics_FPS.

With those caveats in mind, I'll request two products now: