nfs-utils now supports IPv6 when using rpcbind and libtirpc. Please add a USE flag for this. Please also consider revisiting bug 244438. Reproducible: Always Steps to Reproduce:
Created attachment 184512 [details, diff] nfs-utils-1.1.5-r1.ebuild.diff diff to proposed nfs-utils ebuild
Reassigning to net-fs herd.
This is no that easy. You must update init scripts for both nfs and nfsmount to use portmap or rpcbind depending on ipv6 flag.
Same goes for netmount which "depends" on portmap. There are a few way to do it, but like already said, it's not so easy.
Created attachment 190849 [details, diff] Adds support for rpcbind to nfs-utils I use the following patch in my local overlay in order to use nfs-utils with rpcbind. It is quite simple and I am not sure if it is a perfect solution but it might be helpful until someone comes up with a better idea.
nfs-utils-1.1.6-r1 supports USE=ipv6 now
Thank you for IPv6 support. Nevertheless, the init scripts still depend on portmap instead of rpcbind. Since net-fs/nfs-utils-1.1.6-r1 blocks net-nds/portmap it could be enough to just replace "portmap" with "rpcbind". Otherwise the solution I proposed with the patch in comment #5 (the part concerning the init scripts) may be the way to go.
no they dont. review the depend() in the rpcbind init.d script.