As we discussed earlier, it'd be a good idea for openresolv to keep the actual resolv.conf in a runtime-writable directory rather than /etc.
net-dns/resolvconf-symlink is the ebuild doing the symlinking. If you don't mind adding it as PDEP of openresolv, please ping me and I'll file a KEYWORDREQ for it.
`net-dns/resolvconf-symlink` only supports `~amd64 ~x86`, while `openresolv` supports `~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86`, not sure what to do in this case.
Ebuild would be ready to go once we sort out the keywords mismatch.
please join IRC #gentoo-proxy-maint and #gentoo-dev-help we can help you there.
We can not discuss here.
Let's move forward with this, we can add the PDEPEND. Are any other openresolv ebuild changes needed?
(In reply to Ben Kohler from comment #3)
> Let's move forward with this, we can add the PDEPEND. Are any other
> openresolv ebuild changes needed?
go for it, I think
Keywording of resolvconf-symlink done.
The bug has been closed via the following commit(s):
Author: Ben Kohler <firstname.lastname@example.org>
AuthorDate: 2023-06-06 15:12:34 +0000
Commit: Ben Kohler <email@example.com>
CommitDate: 2023-06-07 12:48:07 +0000
net-dns/openresolv: add PDEPEND on resolvconf-symlink
Signed-off-by: Ben Kohler <firstname.lastname@example.org>
net-dns/openresolv/openresolv-3.13.1.ebuild | 2 ++
1 file changed, 2 insertions(+)
1) This breaks installation of openresolv. Openresolv pulls in resolvconf-symlink as a dependency, and resolvconf-symlink fails to install with the following message: "/etc/resolv.conf seems not to be autogenerated. Aborting build to avoid removing user data. If that file is supposed to be autogenerated, please remove it manually. Otherwise, please set USE=-symlink to avoid installing resolv.conf symlink."
2) Even if resolvconf-symlink is successfully installed, it actually doesn't work.
After installation: /etc/resolv.conf is a symlink to /var/run/resolv.conf
After a reboot: /etc/resolv.conf is a regular file again.