Re: New method to load user bundles

[Martin Brecher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Teunissen wrote:
[...]
|
| You may not have realized it here, but you are setting a policy here that
| tells app authors "You have no right to control how your code runs".
|
| Bundles ain't just plugins, well-defined chunks of code that you get to
| tell what to do. They are active entities, able to do anything the app or
| any of the libs can...and there's no way of preventing them from doing
| anything at all, short of not loading them in the first place...
|
| [snip]
|

I haven't thought that much about the following proposals/ideas (which I
had on my mind for some time now), but since this issue has popped up
now, I can as well share them now...

For some needs, I would like some kind of general system policy for
GNUstep defining what a user can set/override. I am thinking mostly
about corporate or computer lab installations here. E.g. I would like to
able to globally set the Local Time Zone and prevent the user to change
it. Same goes for the backend. As well as locking complete parts of the
defaults or locking the defaults in general.

Also I would like to be able to prevent the user from loading any
bundles, libraries at all (i.e. by disabling most use of the ~/GNUstep/*
folders) or to have the system places searched first (i.e. by specifying
System Local Network User to be searched in a special order).

First idea would be to have a file in the System folder defining all
that stuff. But I guess it'd be quite trivial to point GNUstep to a
different location.
Second idea would be to have those policies be compile time settings
(some #defines would be OK for me as are configure parameters...).

I wonder how that's achieved on NeXT / OS X systems (if it's achievable
at all).

Greetings,
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+2WcDkWEEBp53XEURAnPHAJ9BzzwYuHvKevSwNT0fPI5I7WZ99QCg5nDK
R+0xsWfShkW2AeKyEdKNiyo=
=Opn5
-----END PGP SIGNATURE-----