On Mon, 28 Jun 2004, Guenter Knauf wrote:

> I've added a --setup option so that you can now specify different setup
> files; and for NetWare I append the $targetos to the setup filename;

Uh, why? If you support a --setup option, why append anything at all? It makes
better sense to me if the option simply specifies the full path name to the
alternative file.

I don't see any benefit with automatically appending $targetos to the name.

> however I would like to move that line so that it is active for all
> platforms which have a target OS defined.

I would prefer the default setup file name to remain, and allow the option to
change it to whatever you please.

> This would however break any automatic builds of platforms where the
> $targetos is set;

... and with my suggestion, the existing builds would continue working.

> the benefit of this change is that it is then easily possible to build more
> than one target, each with different description, from one curl source
> dir...

I agree with that goal. I think I could fix some of my builds to use the same
source tree too once this fix is made.

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html