Re: [gentoo-dev] Should "server" be a global use flag?

[Jeroen Roovers]

On Mon, 23 May 2011 10:26:49 -0400
"Anthony G. Basile" <blueness@g.o> wrote:

> Hi all,
>
> I was looking at use.desc/use.local.desc to see if the "server" flag
> is global or not.  I was surprised to see that it is not.  There are
> 26 packages that use a local "server" flag and they all say something
> to the effect "Enable ${PN} server support".
>
> Should we not promote this to global with a description
>
>     server - Enable the packages server component

app-admin/bcfg2:server - Installs scripts to be used on the server-side
                         of this app
- If it means, to install a server and scripts, then YES. It should be
  clarified what this flag actually does install as extra.

app-mobilephone/obexd:server - Enables server installation, it's
                               incompatible with obex-data-server
                               provided one
- Is it really really necessary to describe that incompatibility? If
  no, YES.

app-office/akonadi-server:server - Use locally installed database
                                   server.
- Again, what does it mean? Does it install the database server too? If
  yes, YES, but again the description would need to be changed or
  omitted.

dev-libs/tntnet:server - Enable tntnet server daemon
- YES.

dev-python/dap:server - Enable OpenDAP server support
- YES if it actually installs a server/daemon.

dev-ruby/rubygems:server - Install support for the rubygems server
- YES if it actually installs a server/daemon.

dev-vcs/cvs:server - Enable server support
- YES if it actually installs a server/daemon.

games-strategy/wesnoth:server - Enable compilation of server
- YES: if it compiles it, then it installs a server/daemon.

media-plugins/vdr-streamdev:server - Compile the VDR plugin
                                     vdr-streamdev-server that allows
                                     remote systems to access the DVB
                                     cards used for the local VDR
- YES if it actually installs a server/daemon, but the description is
  rather more informative than "enable server component" would be.

media-sound/xmms2:server - Build xmms2 player daemon (otherwise only
                           clients are built)
- YES: it actually installs a server/daemon. That clients will be built
  regardless of this USE flag is irrelevant.

net-analyzer/zabbix:server - Enable zabbix server
- YES if it actually installs a server/daemon.

net-fs/coda:server - Build and install the server components of coda
filesystem. Note: at least one of client/server flags must be enabled.
- YES if it actually installs a server/daemon. REQUIRED_USE should
  replace the need to force either server or client in USE flags.

net-fs/samba:server - Enables the server part
- YES.

net-irc/quassel:server - Build the server binary. If this USE flag is
disabled, the 'core' server binary for quassel is not built, and cannot
be used. You need this enabled on the server, but you might want to
disable it on the client.
- YES. Lots of irrelevant information after the first sentence. If you
  want to explain how to use the ebuild or installed package, then
  write some real documentation and put it on the website.

net-libs/libinfinity:server - Build and install the server binary
including init.d/conf.d-scripts. Needed if you want to host an infinote
server for gobby.
- YES. Again write some documentation instead of abusing a USE flag
  description to explain how the package works.

net-libs/libssh:server - Build with SSH server support
- YES if it actually installs a server/daemon. It's not clear whether
  this just means it compiles in server components into the library it
  installs.

net-libs/wt:server - Compile in stand-alone httpd connector
- Looks like a YES.

net-misc/dhcp:server - Install the dhcpd and dhcrelay programs
- YES.

net-misc/knock:server - Installs the knockd server daemon.
- YES.

net-misc/tigervnc:server - Build TigerVNC server
- YES.

net-misc/tightvnc:server - Build vncserver. Allows us to only build
server on one machine if set, build only viewer otherwise.
- YES. Again, write the HOWTO instead of abusing a USE flag description.

sci-biology/ucsc-genome-browser:server - Install genome browser Web
                                         application. If this flag is
                                         off, only libraries and
                                         utilities from the suite are
                                         installed.
- It isn't clear, but would probably boil down to a YES. The second
  sentence is irrelevant in the context.

sci-mathematics/yacas:server - Build the network server version
- Build the version? You mean build the daemon? If so, YES.

sys-cluster/pvfs2:server - Enable compilation of server code
- Server code? If it builds and installs a daemon, then YES.

sys-cluster/torque:server - Enable compilation of pbs_server and
pbs_sched.
- YES.

sys-fs/owfs:server - Enable building the OWFS server (owserver)
- YES.

(I find myself wondering why so much information is being jammed into
USE flag descriptions that /should/ be available in HOWTOs from
upstream, or else should be written down in HOWTOs we maintain
ourselves - we (Gentoo) used to be good at providing HOWTOs as needed
and it's a good tradition to keep up. It helps the entire open source
community and not just our users, too.)

Anyway, count the YESs above. Maybe some people want to
comment/explain/defend how they wrote their descriptions, so don't
touch them just yet. :)


     jer