[OGo-GNUstep-Port] Re: gstep-make upgrade

[Nicola Pero]

> > Personally I also do not have the impression that this is really 
> > necessary, the gstep-make in OGo works just fine and smaller backward 
> > patches are easy to do. I rather do that instead of tracking a version 
> > all the time.
> 
> I haven't been following the evolution of gstep-make, so I wasn't
> aware of any instability.

gnustep-make has never been unstable (in recent times).

I've personally used it (CVS version) continuously on commercial/live
systems in the past years without problems.

Helge is probably referring to the filesystem change which was implemented
a few months ago.  That's more of a 'backwards incompatible change
requiring you to rebuild the whole system from scratch' rather than
'instability'.

What happened is that at popular request the filesystem structure was
changed to be more similar to Mac OSX.  I personally agree with Helge that
it is sort of a pointless backwards incompatible change which just breaks
deployment systems without improving things much, but many users thought
it was a great step forward - they have been lobbying for years to get
this change implemented.

The switch is sort of incomplete at the moment, as there is going to be
another related change in header location in the next weeks/months, which
should reduce a bit the command-line, and allow easier coexistence of
different library-combos.

After that, I hope we will never have any other change in the future in
the filesystem layout.  I'll oppose any more changes, as I don't see any
point in continuously changing filesystem layout - we did a big filesystem
change this year, I hope all our users are happy now, and that's it - for
a very long time.

Updating to the new filesystem structure has been a bit painful on live
systems because it required rebuilding everything.  A part from that, it
is a smooth transition.