Re: Cocotron

[Stefan Bidigaray]

I understand such a configuration is possible but even though this does work, a small issue does come up, which isn't anything big... under GNUstep.sh things are setup such as:
//Applications
//Library
etc...
because the file assumes a $GNUSTEP_SYSTEM_ROOT/* and if $GNUSTEP_SYSTEM_ROOT=/ you get that.

Also, what I wanted to get through was to set up this type of hierarchy by default as in my opinion it's more intuitive than the current one.  In this case, even if you set your GNUstep root directory to be /usr/lib/GNUstep you get something like:
/usr/lib/GNUstep/Applications;
/usr/lib/GNUstep/Library;
/usr/lib/GNUstep/Local;
etc...

As a side note, I set my hierarchy up similar to yours, except my $GNUSTEP_LOCAL_ROOT=/Local (pretty much like I suggested on the initial post).

Stefan

On 1/2/07, Chris B. Vetter <chris.vetter@gmail.com> wrote:

You can do that by modifying GNUstep.conf, e.g. during installation of
gnustep-make:

        CC=gcc41 ./configure
                --with-system-root=/
                --with-local-root=/
                --with-network-root=/Network
                --with-user-config-file='~/Library/.GNUstep.conf'
                --with-user-dir='~'
                --with-user-defaults-dir='~/Library/Defaults'
                --with-config-file=/share/GNUstep.conf

As you can see, I install everything in / -- that is, I will end up with
  /Applications
  /Library
  /Network (nostalgia)
  /Tools
  /share (which should really be in /Library).

And instead of HOME/GNUstep/... I put everything directly in my home directory.

Been using this 'set-up' for more than a year, and haven't encountered
any problems (aside from moronicly written Makefiles and source code
that insist on using hard-coded path names, like Addresses).

--
Chris