>>>>> "Steven" == Steven Jenkins <sjenkins@ms.com> writes:
Steven> [ ... ]
Steven> So what you/we would really like is an install script 'smart' enough
Steven> to put in blah/.platform trees, then do something appropriate (as in
AFS's
Steven> @sys mechanism) to resolve the platform dependencies, figure it all out,
Steven> etc.
I personally think that multi-platform installation is something that
should be addressed outside of a specific software package.
Multi-platform software installations (i.e. collections of software
packages) are typically large, so you probably want to address this
problem uniformly across packages. So I'm not so sure this project is
worthwhile until a more general solution across packages is in place.
AFS's @sys does *not* handle the issue well, since it does not model
upwards/downwards compatibility. (I.e. you install something under
SunOS under /afs/.../@sys with compiled-in paths. Running it under
Solaris doesn't work anymore because the meaning of @sys has changed.)
We had to abandon using @sys completely because of that.
We have a more flexible scheme in place which works independently of
installation specifics of a particular package. (Running under AFS,
but actually completely independent of it.) I'll be happy to describe
it if anyone's interested.
What *definitely* would be worthwhile would be to specify separate
installation directories for the platform-dependent and for the
platform-independent parts of scsh, and to omit installing the
platform-independent stuff.
Cheers =8-} Mike
|