git.iko.soy/typeable/nixpkgs
on master help sign in
mediatomb/gerbera: Add release note information for 21.03

Note that it made into 2 entries, one about new options in the first section. Another in the breaking compatibility section due to the openFirewall option which changes the behavior. Co-authored-by: schmittlauch <t.schmittlauch+nixos@orlives.de>

commit38cfb84ff0cef3e680be150eda5d06ac1b4a1c05 authorAntoine R. Dumont (@ardumont) <antoine.romain.dumont@gmail.com> dateFri 24 Jul 2020, 07:53 (6 years ago) parent299451e
1 file changed+41
nixos/doc/manual/release-notes/rl-2105.xml+41
nixos/doc/manual/release-notes/rl-2105.xml+41
@@ -305,6 +305,24 @@
305305 <literal>/var/lib/powerdns</literal> to <literal>/run/pdns</literal>.
306306 </para>
307307 </listitem>
308+ <listitem>
309+ <para>
310+ The <literal>mediatomb</literal> service is
311+ now using by default the new and maintained fork
312+ <literal>gerbera</literal> package instead of the unmaintained
313+ <literal>mediatomb</literal> package. If you want to keep the old
314+ behavior, you must declare it with:
315+ <programlisting>
316+ services.mediatomb.package = pkgs.mediatomb;
317+ </programlisting>
318+ One new option <literal>openFirewall</literal> has been introduced which
319+ defaults to false. If you relied on the service declaration to add the
320+ firewall rules itself before, you should now declare it with:
321+ <programlisting>
322+ services.mediatomb.openFirewall = true;
323+ </programlisting>
324+ </para>
325+ </listitem>
308326 <listitem>
309327 <para>
310328 xfsprogs was update from 4.19 to 5.11. It now enables reflink support by default on filesystem creation.
@@ -844,6 +862,29 @@ environment.systemPackages = [
844862 All services should use <xref linkend="opt-systemd.services._name_.startLimitIntervalSec" /> or <literal>StartLimitIntervalSec</literal> in <xref linkend="opt-systemd.services._name_.unitConfig" /> instead.
845863 </para>
846864 </listitem>
865+ <listitem>
866+ <para>
867+ The <literal>mediatomb</literal> service
868+ declares new options. It also adapts existing options so the
869+ configuration generation is now lazy. The existing option
870+ <literal>customCfg</literal> (defaults to false), when enabled, stops
871+ the service configuration generation completely. It then expects the
872+ users to provide their own correct configuration at the right location
873+ (whereas the configuration was generated and not used at all before).
874+ The new option <literal>transcodingOption</literal> (defaults to no)
875+ allows a generated configuration. It makes the mediatomb service pulls
876+ the necessary runtime dependencies in the nix store (whereas it was
877+ generated with hardcoded values before). The new option
878+ <literal>mediaDirectories</literal> allows the users to declare autoscan
879+ media directories from their nixos configuration:
880+ <programlisting>
881+ services.mediatomb.mediaDirectories = [
882+ { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
883+ { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
884+ ];
885+ </programlisting>
886+ </para>
887+ </listitem>
847888 <listitem>
848889 <para>
849890 The Unbound DNS resolver service (<literal>services.unbound</literal>) has been refactored to allow reloading, control sockets and to fix startup ordering issues.