I have created an eselect module to manage the symbolic link for the openvpn configuration file. The reason I thought this might be useful is that the post install message in the net-misc/openvpn ebuild specifically says how to manage the symlink manually. My module looks for any .ovpn files in /etc/openvpn/ and allows the user to select one of those as the destination of the symlink. Reproducible: Always Steps to Reproduce: 1. Read post install instructions for net-misc/openvpn ebuild
Created attachment 166958 [details] openvpn module I have attached the module. I based this module off of the module that handles the kernel symlink.
If we include this, then it should be a separate package, as you have already indicated in the Summary. I don't think that the module should be included with the eselect core (i.e., app-admin/eselect). Reassigning to maintainer-wanted and CCing cedk as openvpn maintainer.
I think the current approach with symlinking works very well, and we don't need this.