new package: xwayland
update weston: add xwayland support
pythonPackages: add fig
Packaged cloud-init and its dependencies
Added the cloud-init service
eduke32.nix: disable libpng (can't build with it)
nixos: configure samba and rsync shares with sets
Skip nonreproducible Util test in paramiko
Add paramiko test removal comment
qemu: 2.0.0 -> 2.2.0

Additionally, add support for more external features as well as more
sound system types.
Add mimms, an mms (e.g. mms://) stream downloader
Remove mimms name from description
Add the gtk2fontsel Font Viewer
Bumped PHPStorm to 8.0.2
- also removed fsnotifier from global bin to prevent colisions when multiple Jetbrains IDEs are installed.
Add hyperdex.
dwb: switch to a maintained fork
portix stopped developing and maintaining dwb
disable verbose logging for XServer, fixes #4333

The current options for the XServer produce a huge amount of log messages. The
server produces around 70-80 messages per minute. The most messages look like
this:

display-manager-start[1846]: GetModeLine - scrn: 0 clock: 75200
display-manager-start[1846]: GetModeLine - hdsp: 1366 hbeg: 1414 hend: 1478 httl: 1582
display-manager-start[1846]: vdsp: 768 vbeg: 772 vend: 779 vttl: 792 flags: 9

Since theses messages aren't very useful, I propose to remove the `-logverbose`
and `-verbose` options from the XServer arguments.
virt-viewer: fix SPICE support

* Add missing dependency on 'spice_protocol'

* Fix new build error which came now that ./configure enables SPICE support:

  building virt-viewer
    CCLD     virt-viewer
  /nix/store/b8qhjrwf8sf9ggkjxqqav7f1m6w83bh0-binutils-2.23.1/bin/ld: cannot find -lgdbm
  /nix/store/b8qhjrwf8sf9ggkjxqqav7f1m6w83bh0-binutils-2.23.1/bin/ld: cannot find -lcap
  collect2: error: ld returned 1 exit status

  Fix by adding gddbm and libcap as inputs. Yes, libcap is needed
  _in addition_ to libcap_ng (I tested removing libcap_ng, it failed).

Without this change, virt-viewer cannot be used with guests machines
that uses SPICE.
nixos/virtualbox: Fix warning on enableHardening.

The warning was displayed whenever services.virtualboxHost.enable was
true, but if people were to enable hardening, they'd still get that
annoying message.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
virtualbox: Fix extension pack without hardening.

We divert to the $out/share/virtualbox directory only if we have
hardening enabled, so let's put the extension pack into
$out/libexec/virtualbox instead if we're compiling without hardening.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>