Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <004b01c2c0ad$6dea9300$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Marcel Telka" <marcel AT telka DOT sk>, <cygwin AT cygwin DOT com>
References: <20030120145735 DOT GC28535 AT tortuga DOT etc DOT sk> <20030120150543 DOT GC27717 AT redhat DOT com> <20030120175247 DOT GD28535 AT tortuga DOT etc DOT sk>
Subject: Re: Announce: ioperm-0.2.1 for cygwin released
Date: Mon, 20 Jan 2003 17:57:42 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Marcel Telka wrote:
> On Mon, Jan 20, 2003 at 10:05:43AM -0500, Christopher Faylor wrote:
>> On Mon, Jan 20, 2003 at 03:57:35PM +0100, Marcel Telka wrote:
>>> This software adds support for ioperm() function to Cygwin. This
>>> support includes sys/io.h and sys/perm.h header files (not included
>>> in Cygwin by default) together with development and runtime
>>> libraries.
>>>
>>> News in this release:
>>> * Windows DDK is optional for compilation now
>>> * --prefix=/usr parameter for ./configure script is not mandatory
>>> now
>>>
>>> Homepage: http://openwince.sourceforge.net/ioperm/
>>
>> Is there some reason you're not proposing this as a standard cygwin
>> package?
>
> There are at least two reasons:
> 1. A device driver (ioperm.sys) is required for running ioperm with
> NT/2000/XP
> 2. Windows DDK is required for the driver compilation.
>
> If these drawbacks are acceptable for a standard cygwin package I
> could start ioperm integration with mainstream cygwin net
> distribution.

Personal opinion ONLY:
1. is annoying but probably acceptable if there is some way to install it.
2. is likely a problem. Are you aware that w32api has some ddk support now?
That might be a way around this problem.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/