Message-ID: <462C0F92.D0282878@dessent.net>
Date: Sun, 22 Apr 2007 18:44:50 -0700
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: libusb-win32 auto-install?
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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.

I think it would be very bad to install a (kernel-mode) driver by
default without any action of the user just because they selected a
package to install.

> 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.

That sounds ugly, why can't the user just run foo-config like every
other package that requires configuration?

Brian

--
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/