From: Stefan M. <me...@df...> - 2003-09-30 09:23:15
|
-----BEGIN PGP SIGNED MESSAGE----- Hi Thomas! Yesterday thomas portele wrote: > I have some general trouble with the rich tree. If I want to use sever= al different applications > using one system tree, Why? I think it useful to understand your reasons. Indeed the system tree is not made for this. > the tree is a mixture of application dependant info (e.g. SmartKom.ptp= ) > which our Philips start scripts are always overwriting, system librari= es, and other stuff. True. > Although probably a major task, I would argue to divide the tree in= to 'static' stuff like > scripts and libraries, and dynamic configuration infos (e.g. the DTD= ). Actually Multiplatform can be divided in a "static" part and an application specific part. For some parts this division is obvious. For instance `lib/pca' is not application specific. On the other hand the DTD / Schemas used for the interfaces are clearly application specific. I already noticed this is a problem so I agree with you. Unfortunately in some cases both is closely intermixed - at least in the way things are done at the moment. Yes, I think we need to look into this some time. Until then it might be possible to use symbolic links for the static parts. > Unfortunately I have neither solved my access problems, :-( > nor will I have much time till > the end of the year as I am dividing my time between several > projects. As far as I can foresee the near future I can focus on Multiplatform for the next two months. At the moment I think in December I'll take my remaining holiday and what the next year brings is yet very unclear... > So I will not > be of much help for some time, except raising issues like above :-( But this is a help :-) . After all you are experienced the problems others will have, too. What we really need it that you contribute the Philips version to the CVS tree. Then everybody can work with it. Gr=FC=DFe Stefan -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAgUBP3lLhwnTZgC3zSk5AQEkrwP/WnRRnCmTQ6XUIO64HPFA+FpXcA6y7RPK JiyhCbGFVP7q5hjwxqW+ty0Npgoxv2bmq4HBmVxFU4+8hlUb8M1sksFaD90KQ+uf QYXN4h/fyx0AK9fWDhYoUVPqh26iq26v48eQGflDfaZ8w45fx/g8EmwskBRg+dZf /+eALTJogg0=3D =3Dys9y -----END PGP SIGNATURE----- |