diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-07-06 17:19:27 +0200 |
|---|---|---|
| committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2022-07-07 00:35:17 +0200 |
| commit | 2615c1f17ab1768ebe015d0719cc1ee2e6b092f1 (patch) | |
| tree | 87498ebfa5619742e9a7d2db59bfaf0927f3b2ff /man/os-release.xml | |
| parent | Merge pull request #23918 from yuwata/dissect (diff) | |
| download | systemd-2615c1f17ab1768ebe015d0719cc1ee2e6b092f1.tar.xz systemd-2615c1f17ab1768ebe015d0719cc1ee2e6b092f1.zip | |
os-release: define SUPPORT_END=
Fixes #21764.
I think is very simple, but flexible. The date may be set early, for distros
that have a fixed schedule, but it doesn't have to. So for example Debian could
push out an update that sets a few months before the release goes EOL. And
various tools, in particular graphical desktops, can start nagging people to
upgrade a few weeks before the date.
As discussed in the bug, we don't need granularity higher than a day. And this
means that we can use a simple human- and machine-readable format.
I was considering other names, e.g. something with "EOL", but I think that
"SUPPORT_END" is better because it doesn't imply that the machine will somehow
stop working. This is supposed to be an advisory, nothing more.
Diffstat (limited to 'man/os-release.xml')
| -rw-r--r-- | man/os-release.xml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/man/os-release.xml b/man/os-release.xml index 90527228a2..fd98be5b7a 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -351,6 +351,16 @@ </varlistentry> <varlistentry> + <term><varname>SUPPORT_END=</varname></term> + + <listitem><para>The date at which support for this version of the OS ends. (What exactly "lack of + support" means varies between vendors, but generally users should assume that updates, including + security fixes, will not be provided.) The value is a date in the format + <literal>YYYY-MM-DD</literal>, and specifies the last day on which support <emphasis>is</emphasis> + provided.</para></listitem> + </varlistentry> + + <varlistentry> <term><varname>LOGO=</varname></term> <listitem><para>A string, specifying the name of an icon as defined by <ulink |