Requirements on GSPM

1. R001: the end-user may be non-root on his own machine.
2. R002: the "end-user" may be a team => team central installations (eg. stable releases) + people-specific installations (eg. beta releases, personal patches) + search engines to enable object overlapping.
3. R003: various releases and/or patched releases may be installed and/or used in parallel (eg. multiple gcc, multiple SystemC, multiple SPG object releases, various cross-compatibility rules) by different members of the same team, or even by the same person at the same time (even if probably in different xterm sessions).
4. R004: the final combination (eg. which gcc, which SystemC, which objects) may be decided also at configuration time, not only at installation time. For example, some initial releases of SystemC (e.g. 2.1) will be never compatible with gcc_4.x - which may be fixed at installation time - some releases of our objects (e.g. cosimulation objects) will be compatible only with IUS (or any other future SystemC packages which will support cosimulation) - which may be detected only at configuration time (ie. are such objects required by the current platform, with all its configuration flags?).
5. R005: each object shall be able to define its own installation process, even if configure/make/make install or a simple gtar xvzf should be the most common ones.

I'm not sure I agree with R005. I think from the perspective of the user, the less difference the better?

PageComment2(commentfirst=1,nosmiley=1,articleview=1)