I'm all for it! It will solve a problem I have. Is this a big change -
will it take long to do?
I've had lots of problems with classpaths, and have the feeling that
adding one or two variables wont solve all of them. Will it?
I prefer waiting a bit longer (and helping out if I can) than only fix
things halfway.
/Anders
Markus Nolte wrote:
> This is a good idea. We can use NEXT_HOME_ROOT instead of
> ${user.home}/Library for things like wobuild.properties (e.g. NEXT_HOME_ROOT
> =${user.home}/.WOLips).
>
> Uli, what do you think about this?
>
>
>>Here's an approach that might solve the
>>problem of /System and /Local on OSX vs. c:/Apple and C:/Apple/Local on
>>NT. I propose we use the GNUstep approach.
>>On OSX
>>NEXT_ROOT = /
>>NEXT_SYSTEM_ROOT = ${NEXT_ROOT}/System
>>NEXT_LOCAL_ROOT = ${NEXT_ROOT}/Local
>>NEXT_HOME_ROOT = ${HOME}/.OpenStep (or whatever)
>>[I'm used to Nextstep and Mach, not OSX, so HOME_ROOT might be wrong in
>>this example]
>>
>>On Windows
>>NEXT_ROOT = C:/Apple
>>NEXT_SYSTEM_ROOT = ${NEXT_ROOT}
>>NEXT_LOCAL_ROOT = ${NEXT_ROOT}/Local
>>NEXT_HOME_ROOT = ${USERPROFILE}/.OpenStep
>>
>>The above means that NEXT_SYSTEM_ROOT and NEXT_LOCAL_ROOT could be the
>>basis of the patterns, obviating the issue around /System/Local
>>
>>Regards,
>>Christian.
This archive was generated by hypermail 2.0.0 : Fri Jan 10 2003 - 08:40:01 EST