From: Stefan M. <me...@df...> - 2003-09-29 10:23:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hi! 3 days ago Stefan Merten wrote: > I'm wondering about a good alernative to `SK_HOME'. ... My final conclusion was to have an uniform method consisting of two steps: * In general the pointer to the root of the system tree is a parameter to the `SmartKom' / `Multiplatform' script. This parameter would be given by an option. I think `-h'/`--home' is a good idea. * The `SmartKom' / `Multiplatform' script sets environment variable `MP_HOME' so all subsequent processes inherit this value treating it as a constant pointing to the rich structure system tree. Any process needing access to the system tree can obtain it by the environment variable then. This needs no changes in existing software (beyond `SK'/`MP' changes). Of course the environment is modified by `SmartKom' / `Multiplatform' according to `local/SmartKom.env' / `local/Multiplatform.env' as usual. As an alternative `MP_HOME' might be set in the environment. However, I think a warning suggesting use of the respective option is a good idea. This allows for things like alias SmartKom 'Multiplatform --home $SK_HOME' > Also we need to know which operations are actually affected by > `SK_HOME'. Of course running a Multiplatform based system is strongly > affected by `SK_HOME'. The other main operation which comes to mind is > running `make'. Are there any more? Ah - debugging is an additional > case. Some of the debugging tools need to run in the (correct) > Multiplatform environment. Anything else? Does anything else come to mind? In particular: Does any operation come to mind where the concept outlined above may not work? What about Windows? I'll start changing `SK'/`MP' `smartkom'/`multiplatform' now in all existing packages. Gr=FC=DFe Stefan -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAgUBP3gCLwnTZgC3zSk5AQGb4gP6AjvzkahxcFnxIhzdh0xqQ6t3lHPU1sLd os/BIhvKQlbSglSc3oxxWr3zKqUmY72YRByrrsU2oNNyiWU5seswdtyhXyaq19fl TGctodEhj1kdf5EHf7FE18XaIM5j+BwuHDgvWxgg1mjcTZHjFsG+JWf79wsFTO8q 3cx6XhsAKKc=3D =3DDNIt -----END PGP SIGNATURE----- |