Ebuild for GNU Virtual Private Ethernet gvpe-2.01.ebuild included a example config a confd file and a init script tested and works on x86 and amd64 Reproducible: Always Steps to Reproduce:
Created attachment 155721 [details] gvpe.ebuild init script and some config files
I willing to proxy maintain this ebuild.
blackd, I suggest you to maintain ebuild in sunrise overlay first: http://overlays.gentoo.org/proj/sunrise/wiki It's a very good start and if everything will be Ok there, then we'll move and maintain with your help it in official tree. Before asking for commit into sunrise, please, fix the following: 1. Please, attach plaintext files to bugzilla. It's much easier to review. 2. There is no metadata.xml. Please, put yourself as maintainer there. 3. ebuild uses +useflag syntax but EAPI=1 is not defined there. 4. Do you really have all this, ~amd64 ~arm ~ppc ~sparc ~x86, hardware? If you don't have put only keyword for architecture you really tested ebuild on. All other keywords should be dropped. 5. Why do you use CONF_PARAM="$(use_enable nls) " use dns && CONF_PARAM="$CONF_PARAM $(use_enable dns) " [snip] econf $CONF_PARAM It's much better to put everything as a parameter to econf: econf $(use_enable nls) $(use_enable dns) if for some reason use_enable does not work, please, tell the reason in comments. also use "local": local CONF_PARAM 6. dodoc, newinitd and similar functions don't die on their own. Please, add || die there. 7. run repoman full in ebuild directory and fix warnings. 8. initscript should use start-stop-daemon to manage connections. Also seems that you have typo there: rec*o*nnect Enjoy, and ask questions here, by mail or find me in irc on FreeNode (my nick pva).
Created attachment 164365 [details] updated 2.01 ebuild
Created attachment 164367 [details] version 2.2 ebuild
Created attachment 164371 [details] here it is
Created attachment 164372 [details] to keep repoman happy
Created attachment 164374 [details] files/gvpe.rc
Created attachment 164375 [details] files/gvpe.conf.example
Created attachment 164377 [details] files/gvpe.confd
Created attachment 164378 [details] files/if-up
The gvpe ebuild is now in the Sunrise overlay and can be found at: http://overlays.gentoo.org/svn/proj/sunrise/reviewed/net-misc/gvpe/
version 2.21 is now in sunrise get it from here http://overlays.gentoo.org/svn/proj/sunrise/reviewed/net-misc/gvpe/
https://lwn.net/Articles/573952/ Apparently this never made it into canonical Portage?
After several attempts to update the ebuild in sunrise I'm posting it here.
Created attachment 374718 [details] version bump of gvpe to 2.24 converted to eapi 5
Clarification: 1. The sunrise people mostly ignored my review requests. 2. Since 2.25+ are incompatible with my set up I'm unable to test it for now.
(In reply to blackd from comment #17) > Clarification: > 1. The sunrise people mostly ignored my review requests. Sorry about that. Unfortunately there is only one sunrise member active currently, and he hasn't been around so much lately.
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
