We "recommend" the kernel driver and do not "require" it in order to
not break cases where beep is installed on systems other than
bare-metal PC hardware such as containers.
This assumes the people using the "beep" package can deal with a
"beep" invocation not producing a beep on those other systems.
The alternative would be to "require" the kernel driver which would
mean that you could not install beep inside a container, even if
that container is run in a priviledged way with access to the host's
pcspkr.ko.
While the kernel supports more speaker drivers, the only hardware
platforms with a speaker driver supported by Fedora use pcspkr.ko
(PCSPKR_PLATFORM in the kernel config).
Slightly (but not quite) similar packages would be floppy-support
and joystick-support which both "require" their respective kernel
drivers, but they make less sense inside containers.
Summary of the changes in the beep-1.4.4 release:
* ship our own modprobe.d and udev rules.d files
* install udev rules into /usr/lib/udev/rules.d/
(if the sysadmin want their own rules, they can
add them to /etc/udev/rules.d/)
* new out of the box permission setup: allow local
users and "beep" group
* add note on using sox/play with modern sound infrastructure
* adapt beep(1) man page to mention README.fedora
* set compiler flags for "make install" (just in case)
* install extra source files directly from %{SOURCEn}
* ship the installed doc files as %doc (no need to install
them from source)
