I have written a ebuild for tinc. Its an vpn implementation. An init script is included. Reproducible: Always Steps to Reproduce: 1. cd $PORTDIR_OVERLAY 2. tar xjf tinc_ebuild.tar.bz2 3. emerge -v $PORTDIR_OVERLAY/net-misc/tinc/tinc-1.0.2.ebuild Actual Results: I had tinc installed. Expected Results: the result was expected, nothing went wrong.
Created attachment 20868 [details] the ebuild
Tim - please see: http://emu.gentoo.org/~liquidx/ebuildmistakes.html in particular: Common Ebuild Submission Mistakes, point 1 Thanks.
Created attachment 20936 [details] The plain ebuild Here is the plain ebuild, an init script will folow since its needed.
Created attachment 20937 [details] The init script the init script for ./files/
Created attachment 20989 [details] init script with support for multiple tinc networks this init script which supports multiple networks network configuration file is /etc/conf.d/tinc.networks: # tinc networks NETWORK: first_vpn NETWORK: second_vpn .... network configuration directories are /etc/tinc/first_vpn/, /etc/tinc/second_vpn/ ... log files: /var/log/tinc.first_vpn.log, /var/log/tinc.second_vpn.log ... pid files: /var/run/tinc.first_vpn.pid, /var/run/tinc.second_vpn.pid ...
Okay I will work on adding this ebuild but additional testing of the attached files would be greatly apreciated as I have no experience with tinc personally.
Ebuild added.
bazik@gentoo.org added the init script... have a nice day :)
working fine for me well, maybe it would be worth of extending ebuild to create default /etc/conf.d/tinc.networks file (ONLY if it does not exist yet) with content like: # List of configured tinc networks # # Syntax: # NETWORK: network_name # for each tinc network configured. ---- unfortunately, i'm not very familiar with creating ebuild scripts ...
works for me also (with small problems, but it works :-)
Created attachment 35869 [details] Fixed init script Bug fix of init script -> there should be numeric comparison for number of defined networks