Created attachment 375032 [details] openvpn-2.3.3.ebuild net-misc/openvpn-2.3.3 version bump trivial version bump I also updated the dependencies to the versions in portage tree, see attached patch for quick perusal of the trivial changes
Created attachment 375034 [details, diff] openvpn-2.3.3.ebuild diff relative to openvpn-2.3.2.ebuild openvpn-2.3.3.ebuild diff relative to openvpn-2.3.2.ebuild
Why did you update the dependencies? That's not really how this works. Looks like we do need to bump the PolarSSL version to 1.2.10, according to the changelog. And possibly disable the eurephia USE flag.
I updated the dependencies to the smallest stable versions available in the portage tree, which is only cosmetic in this case since all versions available satisfy OpenVPN according to the 2.3.3 changelog and INSTALL: - dev-libs/openssl-0.9.8y - dev-libs/lzo-2.06 - dev-libs/pkcs11-helper-1.10 - net-libs/polarssl-1.3.0 This seemed reasonable, did I do something stupid and wrong? If so, please tell me to RTFM ;) (I did, but this is the first ebuild I submit) I did not try emerging with polarssl (masked by hardened profile).
Done: + 22 Apr 2014; Dirkjan Ochtman <djc@gentoo.org> +openvpn-2.3.3.ebuild: + Version bump openvpn to 2.3.3 (bug 507758). It doesn't make much sense to me to restrict dependency versions based on what's in the tree. The ebuild tries to describe what the package needs. If someone wants to use this ebuild in another context, they wouldn't be tied to versions of other packages that happen to have been removed from the portage tree.
