Re: different CVS_SERVER for different hosts

[Paul Edwards]

"Mark D. Baushke" <mdb@cvshome.org> wrote in message 
news:mailman.2935.1067674395.21628.bug-cvs@gnu.org...
> For what it may be worth, gnu make is at version 3.80 these days...

Yeah, but you don't necessarily need to be compatible
with the latest version.  I don't know what the requirements
are for the makefiles distributed in CVS.

> ISO/IEC 9945-1, ANSI/IEEE Std 1003.1 Second Edition 1996-07-12 specifies
> that <time.h> will define what is needful to support a nanosleep() call.
> nanosleep() was introduced in POSIX 1003.1b-1993, but was not part of
> 1003.1-1990.

Sure.  This is fine.  Maybe what is needed is separate
posix directories.  A posix1990 which only enables those
things that are guaranteed by 1003.1-1990, and a
posix1993 ...

> So, a program may or may not see nanosleep() in <time.h> depending on
> the revision of the date of the POSIX 1003.1 specification being used
> by the host.

Sure.

> The point here is that POSIX support is a mixture of common practise and
> mandated minimum requirements. So, the configure script will likely still
> be useful to determine the capabilities of the host system.

Sure!  Nothing wrong with such a script which can be used
on systems.  But I don't think there should be such a requirement
to run such a thing.  It should be possible to say "This product
is Posix <version xyz> compliant and will thus work on any
Posix <version xyz> comliant system".

> It is also entirely possible that an OS might support the nanosleep()
> function call without being fully POSIX compliant...

Sure.  Which is why the #ifdef HAS_NANOSLEEP is indeed
useful, so that such systems will still get that feature.

I don't have a problem with that.  I guess what it boils down
to is that I expect a config.h which specifies only those
features that Posix enables.

To enable CVS to compile on Posix 1003.1-1990 environments
"out of the box".  If the user wants to manually tweak the config.h
to provide extra features that his environment has, that aren't
Posix-compiant, that's fine.  And maybe if they install the right
software, they may even be able to get "configure" to generate
that automatically, which is great!  But not make it a requirement.

>> If you have no way to sleep, in fact, C89 provides no such
>> facility, then what do you expect to happen on such an
>> environment where the ability to sleep does not exist?

> Well, that might depend on the OS environment. Some systems might be
> compatible with the Single UNIX Specification (SUSv2) as defined by the
> Open Group in 1997 and allow for either or both of the usleep() call or
> the select() function to be called with a timeout.

Sure, I don't have a problem with that.

I just expect the pre-generated config.h files to be available,
so that I have a starting point for adding my own tweaks for
my own system which may not be completely Posix 1990
compliant.  If I use a non-compliant system, I fully expect to
have it either not compile or require tweaking.

BTW, the stuff I posted had :ext: support removed.  I've
got a new one which works with :ext: and I can reproduce
the hanging problem, so you know what that means.  :-)

BFN.  Paul.