Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<00b301c21b02$9aca50f0$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin-developers AT cygwin DOT com>
References:	<001001c21afa$8123fa00$6132bc3e AT BABEL> <20020623212533 DOT GA28284 AT redhat DOT com>
Subject:	Re: Release of the <sys/ipc.h> and <sys/shm.h> files
Date:	Sun, 23 Jun 2002 23:09:11 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

"Christopher Faylor" <cgf AT redhat DOT com> wrote:
> If the files shouldn't be included in the distribution, they either
> shouldn't be in the repository or they should be protected against
> accidental use.

My preference would be to exclude them from the distribution.  People
already have to edit <sys/types.h> and "cygwin.din" then re-build;
asking them to fetch the header files from CVS isn't too great an
extra effort for the moment.  The problem with that is that there is
code in the DLL now that requires those headers, so they're needed to
build the DLL.  So, removing the headers would imply removing all the
cygserver shm code too.

Perhaps someone can come up with a better (i.e. easier) solution than
such wholesale removal.  Maybe, as you suggest, some sort of
protection: a USE_EXPERIMENTAL_CYGWIN_FEATURES flag (or something
better named, of course :-)) that is needed to use the headers; that
could then be defined for the DLL and cygserver builds, but not
otherwise.

// Conrad

- Raw text -