An OpenAFS server may be run on a system that does not support an AFS client. For instance, a VPS with a monolithic kernel. openafs-kernel may not build or kernel sources may not even be available. Please do not depend on openafs-kernel unconditionally - perhaps a USE flag is in order? Reproducible: Always Steps to Reproduce: 1. Try to install openafs on a machine with no kernel sources installed 2. See the kernel sources pulled in as deps 3. Fail
how about a blocker ? -RDEPEND="~net-fs/openafs-kernel-${PV} +RDEPEND="!<net-fs/openafs-kernel-${PV} + !>net-fs/openafs-kernel-${PV}-r999
a better solution would be completely seperated server and client ebuilds
If I understand correctly, you can either use openafs-kernel or you can use built-in kernel AFS support. So the client wouldn't have to depend on openafs-kernel either. A warning that either the kernel option or the ebuild are needed for the client to work should suffice.
Hi, any news here? Mandatory openafs-kernel is indeed superfluous.
Though openafs-kernel is mandatory for openafs client and may be omitted only for server. Standard kernel module is a completely different solution which allows to mount AFS volumes without net-fs/openafs client at all, though with somewhat limited functionality (see Documentation/filesystems/afs.txt in kernel docs).
There is little point in separate client and server ebuilds, because servers depends on client and other distributions doesn't do such separation to my knowledge. In 1.6.11 I added USE="modules" to control where kernel module should be build, enabled by default.
