1. emerge runit, a new symlink is created ls -ld /etc/runit/runsvdir/current lrwxrwxrwx 1 root root 2 Feb 8 11:22 /etc/runit/runsvdir/current -> default/ 2. i changed it to "my/" 3. re-emerge runit expected result: symlink to "my/" actual result: symlink to "default/" reasons * when by *.ebuild design it's a symlink, it's for user customization * user settings should not be overwritten
You could add a CONFIG_PROTECT entry to /etc/env.d yourself. I guess that would work.
I can't take the risk to reinstall it yet. but i /etc/ is already under protection. i'm not talking about /var/service but /etc/runit/runsvdir/current # emerge --info |grep CONFIG_P CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt /var/qmail/control" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/ /etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CONFIG_PROTECT="/etc <- this should protect it already
This is fixed in 2.1.2. Everything under /etc/runit/runsvdir now will not be owned by portage, like /etc/init.d for OpenRC based systems. That subdirectory is now fully user configurable.
