I'd like to keep support for the root .GNUsteprc file as well, at
least
until we decide to depreciate it.
I thought that now was right time to do so. It does not add
functionality,
but the same level is provided by the new GNUstep.conf along with other
benefits. One might consider the new configuration file a sort of
upgrade of
the old one, albeit one which requires changes and moving the file.
I think having a root .GNUsteprc which can over-ride GNUstep.conf
makes things
more complex without giving us any benefits.
Why did you take out the creation of a secure subdirectory of temp?
This is a bigger question.
Firstly, the existing code isn't really secure. You can circumvent it.
I
looked at changing that but things start getting quite complex.
Secondly, the OpenStep and Cocoa behaviour is simply to return the
temporary
directory.
Now, what is the right behaviour from an API perspective? Well, on
one hand
we want a place where we can create temporary files in a secure and
safe way.
Often, the goal is a temporary file. Pure and simple. No need for a
whole
directory.
On the other hand, sometimes we want to discover where {temp} actually
is. For
example, if I want to find "/tmp/.X11-unix".
Additionally, there are systems which use extended attributes and
capabilities
for more secure/flexible behaviour.
In light of these things, I think that the right thing for
NSTemporaryDirectory() to do is to return the path to the temporary
directory.