OpenSSH needs a 'server' USE flag to install the client files only, since not everyone wants both the client and the server on all their computers (most binary based distributions provide two distinct OpenSSH packages for this reason). Reproducible: Always
(In reply to Scall from comment #0) > OpenSSH needs a 'server' USE flag to install the client files only, since > not everyone wants both the client and the server on all their computers > (most binary based distributions provide two distinct OpenSSH packages for > this reason). > > Reproducible: Always ugh no. I know debian and others do but why really? Does it bother you having this one extra file?
(In reply to Anthony Basile from comment #1) I don't see why users should have sshd and related files intalled when they don't need them. Gentoo is about choices, isn't it? I think it's a contradiction in terms that other distributions, like the one you mentioned, give you more choice than Gentoo in this respect.
This is going to be a pain to do. From the upstream package, there's at least, /etc/ssh/sshd_config /usr/share/man/man5/sshd_config.5.bz2 /usr/lib64/misc/sftp-server /usr/share/man/man8/sftp-server.8.bz2 /usr/sbin/sshd /usr/share/man/man8/sshd.8.bz2 And Gentoo adds the init, conf, and systemd files. Those are easy enough to wrap in a "use server" block, but the ones that come from upstream will be annoying to remove because we have to either, 1) Get rid of the emake ... install line, and install everything manually. 2) Keep the emake ... install, and remove all of the upstream files manually. I'm not saying the request isn't legitimate, but it would be a lot less intrusive if you could talk upstream into adding a --server option to their ./configure.
Arguably, you could probably use both the 'server' and 'client' USE flags, like what net-fs/samba does, if all you needed were the OpenSSH libraries and no client or server binaries. But I agree, this should be made into an upstream feature request that we can later implement.
(In reply to Joshua Kinard from comment #4) > Arguably, you could probably use both the 'server' and 'client' USE flags, > like what net-fs/samba does, if all you needed were the OpenSSH libraries > and no client or server binaries. But I agree, this should be made into an > upstream feature request that we can later implement. Actually there's a good chance of this being accepted because many distros do this.
(In reply to Joshua Kinard from comment #4) Yes, a 'client' USE flag would be needed as well. > But I agree, this should be made into an upstream feature request Here it is: https://bugzilla.mindrot.org/show_bug.cgi?id=2298
Upstream WONTFIX'd this, should we too? Without upstream help it would make the ebuild a mess, and realistically, what would we gain? We still have to build both client and server. If this is just about installed files then INSTALL_MASK can be used in emergencies.
