Re: RFC: Framework support in -make

[Nicola Pero]

> > > because in real life the problem is not really moving frameworks from
> > > one directory into another on the same machine, but binary distribution
> > > between machines with the same frameworks installed in different dirs.
> > 
> > This is also not a problem. The point behind this idea is to make
> > frameworks self-contained, so that binary distribution becomes easy.

PS: thinking about it, you could improve on your -rpath proposal by using
multiple -rpaths.  You could use 3 -rpaths for the 3 GNUstep domains, that
would make it more difficult to break.

It still wouldn't work if you share/dispatch the binary into a machine
with the domains with different locations though.

One problem seems to be that if you have an application in your home
directory (for example), and you mount your home directory via NFS on
different machines, and if on those different machines the required
frameworks are installed, but in different directories (say, in one
machine framework A is installed system-wide in GNUSTEP_LOCAL_ROOT, while
in another one framework A was not installed and to work around that
you've installed it yourself in your own GNUSTEP_USER_ROOT), then the
application can't work across the machines, because the same executable
(with a single -rpath) should be used on different machines where the
frameworks are in different locations.

That can be worked around a bit by using multiple -rpaths ... still for
anything involving the user root (as in the example), you probably need
LD_LIBRARY_PATH anyway (your home dir could be mounted on different dirs
on different machines!), and then -rpaths loose appeal.

You have a similar problem with any application (or framework depending on
other frameworks) installed into GNUSTEP_NETWORK_ROOT - which is meant to
be mounted on machines which could be very different - and because that's
meant to be shared over a heterogeneous network, maybe someone could want
to share it over machines which have the GNUstep domains in different
locations, then that can't be worked around.