Re: porting to GNUstep from OSX

[Alexander Malmberg]

Helge Hess wrote:
> On Freitag, 11. Juli 2003, at 12:48 Uhr, Nicola Pero wrote:
> > So you don't have many reasons to use autoconf, unless you need to use
> > a
> > special third-party library/package outside of gnustep (say, a specific
> > audio or image C library for example).
> 
> I would still like to see a "standard repository" for that ! Let open a
> registry of things people want to check for, add them to gstep-make.
> I've found configure scripts to check too often for simple things again
> and again.
> (like gethostbyname_r).

Use NSHost. ;-)

> Would like a global gstep-make config.h which already covers most (all
> ;-) aspects one might check for.

I disagree; I don't think something like this belongs in -make. -make
should help manage GNUstep packages; the if and how of checking for
external c libraries/functions should be left to the apps/tools that
actually require them.

Additionally, I think there would be big issues with keeping the
repository up to date when packages are installed/upgraded/removed. For
example, I install the dependencies for an app when I install the app;
if the app used -make's repository, I'd have to reconfigure/reinstall
-make to get the app to notice that the dependency really is satisfied.

- Alexander Malmberg