Revert "mediatomb/gerbera: Add release note information for 20.09"
This was added to a release note when it's a feature not landing in that release.
This reverts commit a007e07abb
.
This commit is contained in:
parent
b6c7e8c66b
commit
8cae8e54a1
1 changed files with 1 additions and 40 deletions
|
@ -232,28 +232,6 @@ GRANT ALL PRIVILEGES ON *.* TO 'mysql'@'localhost' WITH GRANT OPTION;
|
||||||
<filename>testing-python.nix</filename> respectively.
|
<filename>testing-python.nix</filename> respectively.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
The Mediatomb service declares new options. It also adapts existing
|
|
||||||
options to make the configuration generation lazy. The existing option
|
|
||||||
<literal>customCfg</literal> (defaults to false), when enabled, stops
|
|
||||||
the service configuration generation completely. It then expects the
|
|
||||||
users to provide their own correct configuration at the right location
|
|
||||||
(whereas the configuration was generated and not used at all before).
|
|
||||||
The new option <literal>transcodingOption</literal> (defaults to no)
|
|
||||||
allows a generated configuration. It makes the mediatomb service pulls
|
|
||||||
the necessary runtime dependencies in the nix store (whereas it was
|
|
||||||
generated with hardcoded values before). The new option
|
|
||||||
<literal>mediaDirectories</literal> allows the users to declare autoscan
|
|
||||||
media directories from their nixos configuration:
|
|
||||||
<programlisting>
|
|
||||||
services.mediatomb.mediaDirectories = [
|
|
||||||
{ path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
|
|
||||||
{ path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
|
|
||||||
];
|
|
||||||
</programlisting>
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
@ -896,23 +874,6 @@ CREATE ROLE postgres LOGIN SUPERUSER;
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
The mediatomb service is now using the new and maintained <literal>gerbera</literal>
|
|
||||||
<literal>gerbera</literal> fork instead of the unmaintained
|
|
||||||
<literal>mediatomb</literal> package. If you want to keep the old
|
|
||||||
behavior, you must declare it with:
|
|
||||||
<programlisting>
|
|
||||||
services.mediatomb.package = pkgs.mediatomb;
|
|
||||||
</programlisting>
|
|
||||||
One new option <literal>openFirewall</literal> has been introduced which
|
|
||||||
defaults to false. If you relied on the service declaration to add the
|
|
||||||
firewall rules itself before, you should now declare it with:
|
|
||||||
<programlisting>
|
|
||||||
services.mediatomb.openFirewall = true;
|
|
||||||
</programlisting>
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
The GNOME desktop manager no longer default installs <package>gnome3.epiphany</package>.
|
The GNOME desktop manager no longer default installs <package>gnome3.epiphany</package>.
|
||||||
|
|
Loading…
Reference in a new issue