Le Wednesday 7 July 2010 10:46:50, Gert Doering a écrit :
> Hi OpenWRT folks,
>
> I'm one of the current OpenVPN developers, and happy OpenWRT user, but
> have not yet fully figured out how the OpenWRT development model works
> ("who decides what, who commits where, etc.") - so bear with me :-)
>
> OpenWRT has an OpenVPN package containing the current stable release
> (2.1.1), and this is a good start.
>
> OTOH, that package does not have any sort of IPv6 support, which means
> that IPv6-on-OpenWRT users need to compile their own OpenVPN package,
> which is not that easy for non-developers.
>
> I have dabbled a bit with the OpenWRT build system and created a package
> Makefile that seems to work (as in: it fetches the right source archive
> and builds an .ipk that 'works for me'). It shares the "files/" stuff
> with the existing openvpn package. It is attached, in case you want to
> tell me what I should do differently :-) - build instructions have
> been put here (again, feedback welcome):
>
> https://community.openvpn.net/openvpn/wiki/OpenvpnDevelPackageForOpenWRT
>
>
> Now, for the interesting bit: what is the way to get a new package into
> the OpenWRT package feed? And when it's in there, how to get it updated
> when the upstream release changes? (OpenVPN development uses weekly
> snapshots for 'platform builds', e.g. FreeBSD ports, and my OpenWRT
> Makefile is based on these).I applied in r22445 your Makefile in a new package, called openvpn-devel (just like we have a quagga-unstable package). Right now it uses the openvpn files/ directory and therefore shares the config and init script, this can be changed later. -- Florian
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
