On 4/22/07, Samuel Thibault wrote:
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit :
> Or you could follow the model of the ioperm package, which requires you to
> manually run "ioperm -i" to install the .sys file.
>
Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit :
> I think i
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit :
> Or you could follow the model of the ioperm package, which requires you to
> manually run "ioperm -i" to install the .sys file.
>
Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit :
> I think it would be very bad to install a (ker
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 packag
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 depend
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 exa
Samuel Thibault wrote:
> Hi,
>
> Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
>> A good reason for this division is to allow for user input during the
>> configuration step, which "setup.exe" doesn't have support for.
>
> It doesn't need user input.
>
>> If running your libu
On 23 April 2007 00:16, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault wrote:
On 22 April 2007 14:49, Morgan Gangwere wrote:
> On 4/22/07, Brian Dessent wrote:
On 22 April 2007 15:45, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
:-) Thank you Morgan!
On 4/22/07, Samuel Thibault wrote:
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your libu
Samuel Thibault wrote:
> Hi,
>
> Installing my libusb-win32 package doesn't automatically install the USB
> driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> this way for safety.
>
> However, some user reported that it would be better that the
> installation is automatica
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation is automatically performed (since if one installs
li
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your libusb-install is more like a configuratio
Hi,
Morgan Gangwere, le Sun 22 Apr 2007 08:44:55 -0600, a écrit :
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
> >Installing my libusb-win32 package doesn't automatically install the USB
> >driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> >this way for safety.
> >
>
On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation i
13 matches
Mail list logo
