> -----Original Message----- > From: Alon Bar-Lev [mailto:alon.bar...@gmail.com] > Sent: zondag 6 mei 2012 18:55 > To: openvpn-devel@lists.sourceforge.net > Subject: [Openvpn-devel] [RFC] Split plugins into their own > repositories > > Hello, > > Now, I also have the courage to ask one more question regarding > build.... > > We currently have: > - auth-pam > - defer > - down-root > - examples > > Distribution wise it will be best to allow admin to install plugins as > own package which requires openvpn, allowing select specific plugins, > while each has own release cycle and versioning. > > I already made the openvpn-plugin.h available in /usr/include, so there > is no real reason to keep the plugins in openvpn tree, as they can be > complied using their own separate build system. > > for example, if we take RHEL, we can install the following to use the > auth-pam plugin: > > openvpn > openvpn-plugin-auth-pam > > To build plugin we need openvpn-devel. > > What do you say? > > BTW: next will be probably to split out the contrib... :) > > Alon >
Aren't we going a little far in the whole splitting business? I though splitting the build system off was already taking it a too far. These plugin and contrib. directories are directly related to the current version of OpenVPN. Having them in the same tree, especially one that has already been cleaned up by giving it a separate src directory. My vote therefore goes towards keeping them inline! Adriaan
