On Tue, Mar 17, 2015 at 04:36:56PM +, Eitan Eliahu wrote:
>
> I don't have a strong opinion but once the installer is included in the OVS
> tree all directory structure is fixed so there is no ambiguity on how or
> where the installer collects the files. It will also avoid having more than
ss it
later).
Thanks,
Eitan.
-Original Message-
From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff
Sent: Tuesday, March 17, 2015 8:26 AM
To: Nithin Raju
Cc: dev@openvswitch.org
Subject: Re: [ovs-dev] OVS Windows MSI installer
On Tue, Mar 17, 2015 at 06:06:47AM +, N
On Tue, Mar 17, 2015 at 06:06:47AM +, Nithin Raju wrote:
> Regarding where the installer code should be located, my vote would be
> to keep this within the OVS repo. A good reason to keep it outside is
> if this code gets reused for installing or packaging non-OVS
> executables. At the Openstac
I think we can drop 32bit support once the 64bit is there.
Thanks!
Eitan
-Original Message-
From: Nithin Raju
Sent: Monday, March 16, 2015 11:10 PM
To: Alessandro Pilotti
Cc: Eitan Eliahu; dev@openvswitch.org
Subject: Re: [ovs-dev] OVS Windows MSI installer
> On Mar 15, 2015, at 7
> On Mar 15, 2015, at 7:54 PM, Alessandro Pilotti
> wrote:
>
>
>
>
>> On 16 mar. 2015, at 03:30, Eitan Eliahu wrote:
>>
>>
>> Alessandro,
>> Yes, no problem of having the installer separate. But, I am confused as I
>> see the two services are there but the driver and the INF file are not
Alessandro,
Thanks for putting out the installer in the open. This is great.
A few more questions from me to the list that Guru has. I had written an MSI
installer long ago, but nothing which involved services and such. So, my
questions may be trivial.
1. How do we handle dependencies? Eg. pthr
On Sun, Mar 15, 2015 at 5:33 PM, Alessandro Pilotti
wrote:
> Hi guys,
>
> As discussed on IRC, here's the Windows MSI installer project that we’d like
> to
> submit for upstream inclusion:
>
> https://github.com/cloudbase/ovs-windows-installer
Thank you for the contribution, Alessandro!
I have
> On 16 mar. 2015, at 03:30, Eitan Eliahu wrote:
>
>
> Alessandro,
> Yes, no problem of having the installer separate. But, I am confused as I
> see the two services are there but the driver and the INF file are not. I
> believe that the MSI file includes everything.
> Do you think you can
tan Eliahu
> Sent: Sunday, March 15, 2015 6:30 PM
> To: Alessandro Pilotti
> Cc: dev@openvswitch.org
> Subject: Re: [ovs-dev] OVS Windows MSI installer
>
>
>
> Alessandro,
>
> Yes, no problem of having the installer separate. But, I am confused as I
> see t
: Re: [ovs-dev] OVS Windows MSI installer
Alessandro,
Yes, no problem of having the installer separate. But, I am confused as I see
the two services are there but the driver and the INF file are not. I believe
that the MSI file includes everything.
Do you think you can add the OS installer
Alessandro,
Yes, no problem of having the installer separate. But, I am confused as I see
the two services are there but the driver and the INF file are not. I believe
that the MSI file includes everything.
Do you think you can add the OS installer script?
Will we have already built MSI file (x
Hi Eitan,
> On 16 Mar 2015, at 02:57, Eitan Eliahu wrote:
>
>
> Hi Alessandro,
> I couldn't find the driver binary as part of the installer. Also, can you
> explain how uninstlaation is done and the case where a driver is already
> loaded.
As explained in the README, the actual binaries are
> On 16 Mar 2015, at 02:41, Ben Pfaff wrote:
>
> On Mon, Mar 16, 2015 at 12:33:09AM +, Alessandro Pilotti wrote:
>> As discussed on IRC, here's the Windows MSI installer project that we’d like
>> to
>> submit for upstream inclusion:
>>
>> https://github.com/cloudbase/ovs-windows-installer
Hi Alessandro,
I couldn't find the driver binary as part of the installer. Also, can you
explain how uninstlaation is done and the case where a driver is already loaded.
Thank you!
Eitan
-Original Message-
From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro Pilotti
Sen
On Mon, Mar 16, 2015 at 12:33:09AM +, Alessandro Pilotti wrote:
> As discussed on IRC, here's the Windows MSI installer project that we’d like
> to
> submit for upstream inclusion:
>
> https://github.com/cloudbase/ovs-windows-installer
>
> The included README.rst provides information on how
15 matches
Mail list logo
