Re: removing the 'make install'-->'make all' dependency

[Alexander Malmberg]

Nicola Pero wrote:
> 
> > > Hi.
> > >
> > > I'm considering removing the dependency of 'make install' from 'make all'.
> >
> > [... snip ...]
> >
> > But you still have all the overhead of having to run su and make twice.
> > In my setup, I have a group of "trusted" users who can install stuff
> > (except where it'd affect root), so I only have to run "make install" as
> > myself to compile and install everything. Keeping root out of the build
> > process seems like a Good Thing, anyway (especially when hacking
> > makefiles; safer to catch "mishaps" as a normal user :).
> 
> Thanks for your comments :-)
> 
> I think a good balance would be to remove the 'install-->all' dependency
> by default, and then add a special option (controlled by an environment
> variable) which would automatically activate the additional
> 'install-->all' dependency again.  It's trivial to build the option into
> gnustep-make.

This isn't necessary. I know that my setup is fairly "special", so I'd
just patch my local copy of -make (just like I've patched to always
compile everything with -g).

> Something like setting GNUSTEP_INSTALL_DEPENDS_ON_ALL=yes in the
> environment (or in a makefile) would automatically turn on the 'install::
> all' dependency, while the default behaviour would be without this
> dependency.  Advanced users with advanced user/group/directory ownerships
> setups can then set GNUSTEP_INSTALL_DEPENDS_ON_ALL=yes in their .bashrc
> (or whatever they use) if they so wish.

This would be ok, too :). Since we already have a couple of these fairly
global flags, would it make sense to add some sort of site configuration
file? (Similar to the autoconf config.site that GNUstep installs.) Then
again, these really are user-level options. Maybe I can get away with
sticking something in Additional/...

- Alexander Malmberg