X-Spam-Check-By: sourceware.org Date: Mon, 23 Apr 2007 03:33:01 +0200 From: Samuel Thibault To: cygwin@cygwin.com Subject: Re: libusb-win32 auto-install? Message-ID: <20070423013301.GE7781@interface.famille.thibault.fr> Mail-Followup-To: cygwin@cygwin.com References: <20070422142332.GN7781@interface.famille.thibault.fr> <462B7BBF.6030300@cygwin.com> <20070422152037.GQ7781@interface.famille.thibault.fr> <462C0B1E.1000002@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <462C0B1E.1000002@cygwin.com> User-Agent: Mutt/1.5.12-2006-07-14 X-IsSubscribed: yes 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 Hi, Larry Hall (Cygwin), le Sun 22 Apr 2007 21:25:50 -0400, a écrit : > The final decision is, of course, yours but I would say that if it's > really just an installation step, there's nothing technically stopping > you from performing the step automatically through a postinstall script, > for example. 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. Samuel -- 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/