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 one copy 
of the same file.

It would be nice also if the installer and the MSI file generated by the 
installer could be built as part of OVS user mode. 

That said, the MSI file itself should be available to users w/o the need to 
build anything and would be related to an OVS release. 

We need get the driver signed and officially pass WHQL (We can discuss 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 +0000, 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 Openstack summit we had discussed that the 
> Cloudbase Neutron plugin installer can also install OVS in the future. 
> If we are talking of such an installer, then it makes sense to put it 
> in a different repo. Since this installer is specific to OVS, I think 
> we should keep it within the OVS repo. (I am probably restating what 
> Ben already said).

I'd like to merge it into the OVS tree, too, after looking at it.  That way we 
don't start to splinter packaging off into other trees and make it more 
difficult for users to find a set of code that works well together.
_______________________________________________
dev mailing list
dev@openvswitch.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=aCQkLNl5h_C4Zsh3AoB2MbzKkws4kvcT99BiiUgzYHY&s=qhwi87O8u3mnEl1sFfbCr2Gtbw4uYPN3tArQdqXiov0&e=
 
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to