X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20070422142332.GN7781@interface.famille.thibault.fr> <462B7BBF.6030300@cygwin.com> <20070422152037.GQ7781@interface.famille.thibault.fr> <462C0B1E.1000002@cygwin.com> <20070423013301.GE7781@interface.famille.thibault.fr> Subject: RE: libusb-win32 auto-install? Date: Mon, 23 Apr 2007 02:43:41 +0100 Message-ID: <00b201c78548$d2547b80$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20070423013301.GE7781@interface.famille.thibault.fr> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 23 April 2007 02:33, Samuel Thibault wrote: > Yes of course (I actually call the uninstallation script at preremove). > But the question is "do we dare installing a driver just because the > user asked for package installation?". > > The problem is that libusb-win32 might be pulled as a dependency of > another package (the upcoming brltty package for instance), in which > case the use may be really be aware that some driver will get installed. > > Maybe I could ship two separate packages: one for the library and one > for the driver, and automatically install the driver at postinstall of > the second package. Or you could follow the model of the ioperm package, which requires you to manually run "ioperm -i" to install the .sys file. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/