Browse Source

update changelog, version numbers and docs for new bugfix release version 1.6.1

tags/v1.6.1
Nils 1 year ago
parent
commit
44a244f44a
13 changed files with 35 additions and 25 deletions
  1. +1
    -0
      CHANGELOG
  2. +6
    -1
      docs/api/index.html
  3. +3
    -3
      docs/index.html
  4. +4
    -0
      docs/src/api/index.adoc
  5. +1
    -1
      docs/src/index.adoc
  6. +3
    -3
      docs/src/jackpatch.1
  7. +3
    -3
      docs/src/non-session-manager.1
  8. +3
    -3
      docs/src/nsm-legacy-gui.1
  9. +3
    -3
      docs/src/nsm-proxy-gui.1
  10. +3
    -3
      docs/src/nsm-proxy.1
  11. +3
    -3
      docs/src/nsmd.1
  12. +1
    -1
      meson.build
  13. +1
    -1
      src/nsmd.cpp

+ 1
- 0
CHANGELOG View File

@@ -9,6 +9,7 @@ External contributors notice at the end of the line: (LastName, FirstName / nick
Absolutely make sure that all clients of the session are closed when closing the session.
This solves the invisible, hidden clients still running even after nsmd quit itself.
Decrease wait time for such clients at session quit from extreme 60s to very long 30s.
For lockfiles fall back to hardcoded /run/user/<user-id> when $XDG_RUNTIME_DIR is not available on the system.


## 2022-04-15 1.6.0


+ 6
- 1
docs/api/index.html View File

@@ -783,6 +783,11 @@ same session by different nsm-daemons, and subsequently GUIs.</p>
cleaned by the operating system, preventing sessions to stay locked after e.g. a power failure.</p>
</div>
<div class="paragraph">
<p>If the system is not XDG-compliant nsmd will try to fallback to <code>/run/user/XXXX</code>, which must exist
according to the Linux Filesystem Hierarchy Standard. I this also fails the user has to
set $XDG_RUNTIME_DIR manually to start nsmd.</p>
</div>
<div class="paragraph">
<p>The lockfile is named after the simple session name combined with a numeric ID for the session
root. It is possible that two <code>nsmd</code> opened two different session roots, both with the same simple
session name, e.g. "my song". Lockfiles are able to distinguish between those and will not prevent
@@ -1921,7 +1926,7 @@ long-standing <code>FIXME</code> in the code by the original author. Or in other
<div id="footer">
<div id="footer-text">
Version API 1.1.2<br>
Last updated 2022-04-15 00:54:20 +0200
Last updated 2022-10-10 17:28:05 +0200
</div>
</div>
</body>

+ 3
- 3
docs/index.html View File

@@ -441,7 +441,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<h1>New Session Manager Documentation</h1>
<div class="details">
<span id="author" class="author">Nils Hilbricht</span><br>
<span id="revnumber">version 1.6.0</span>
<span id="revnumber">version 1.6.1</span>
</div>
</div>
<div id="content">
@@ -556,8 +556,8 @@ Documentation and tutorials for software-developers will be added at a later dat
</div>
<div id="footer">
<div id="footer-text">
Version 1.6.0<br>
Last updated 2022-04-15 00:54:20 +0200
Version 1.6.1<br>
Last updated 2022-10-10 17:28:05 +0200
</div>
</div>
</body>

+ 4
- 0
docs/src/api/index.adoc View File

@@ -224,6 +224,10 @@ Therefore each currently open session creates a lockfile under `$XDG_RUNTIME_DIR
`/run/user/XXXX/nsm/`) that tells `nsmd` to not open such a locked session. This directory gets
cleaned by the operating system, preventing sessions to stay locked after e.g. a power failure.

If the system is not XDG-compliant nsmd will try to fallback to `/run/user/XXXX`, which must exist
according to the Linux Filesystem Hierarchy Standard. I this also fails the user has to
set $XDG_RUNTIME_DIR manually to start nsmd.

The lockfile is named after the simple session name combined with a numeric ID for the session
root. It is possible that two `nsmd` opened two different session roots, both with the same simple
session name, e.g. "my song". Lockfiles are able to distinguish between those and will not prevent


+ 1
- 1
docs/src/index.adoc View File

@@ -14,7 +14,7 @@ A copy of the license has been provided in the file documentation/LICENSE.
:Author: Nils Hilbricht
:iconfont-remote!:
:!webfonts:
:revnumber: 1.6.0
:revnumber: 1.6.1

= New Session Manager Documentation



+ 3
- 3
docs/src/jackpatch.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH JACKPATCH "1" "April 2022" "jackpatch Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH JACKPATCH "1" "October 2022" "jackpatch Version 1.6.1" "User Commands"
.SH NAME
jackpatch \- manual page for jackpatch Version 1.6.0
jackpatch \- manual page for jackpatch Version 1.6.1
.SH DESCRIPTION
jackpatch \- Remember and restore the JACK Audio Connection Kit Graph in NSM
.PP


+ 3
- 3
docs/src/non-session-manager.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH NSM-LEGACY-GUI "1" "April 2022" "nsm-legacy-gui Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH NSM-LEGACY-GUI "1" "October 2022" "nsm-legacy-gui Version 1.6.1" "User Commands"
.SH NAME
nsm-legacy-gui \- manual page for nsm-legacy-gui Version 1.6.0
nsm-legacy-gui \- manual page for nsm-legacy-gui Version 1.6.1
.SH DESCRIPTION
nsm\-legacy\-gui \- FLTK GUI for the 'New Session Manager'
.SS "Usage:"


+ 3
- 3
docs/src/nsm-legacy-gui.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH NSM-LEGACY-GUI "1" "April 2022" "nsm-legacy-gui Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH NSM-LEGACY-GUI "1" "October 2022" "nsm-legacy-gui Version 1.6.1" "User Commands"
.SH NAME
nsm-legacy-gui \- manual page for nsm-legacy-gui Version 1.6.0
nsm-legacy-gui \- manual page for nsm-legacy-gui Version 1.6.1
.SH DESCRIPTION
nsm\-legacy\-gui \- FLTK GUI for the 'New Session Manager'
.SS "Usage:"


+ 3
- 3
docs/src/nsm-proxy-gui.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH NSM-PROXY-GUI "1" "April 2022" "nsm-proxy-gui Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH NSM-PROXY-GUI "1" "October 2022" "nsm-proxy-gui Version 1.6.1" "User Commands"
.SH NAME
nsm-proxy-gui \- manual page for nsm-proxy-gui Version 1.6.0
nsm-proxy-gui \- manual page for nsm-proxy-gui Version 1.6.1
.SH DESCRIPTION
nsm\-proxy\-gui \- GUI for nsm\-proxy, a wrapper for executables without direct NSM\-Support.
.SS "Usage:"


+ 3
- 3
docs/src/nsm-proxy.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH NSM-PROXY "1" "April 2022" "nsm-proxy Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH NSM-PROXY "1" "October 2022" "nsm-proxy Version 1.6.1" "User Commands"
.SH NAME
nsm-proxy \- manual page for nsm-proxy Version 1.6.0
nsm-proxy \- manual page for nsm-proxy Version 1.6.1
.SH DESCRIPTION
nsm\-proxy \- Wrapper for executables without direct NSM\-Support.
.PP


+ 3
- 3
docs/src/nsmd.1 View File

@@ -1,7 +1,7 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.1.
.TH NSMD "1" "April 2022" "nsmd Version 1.6.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
.TH NSMD "1" "October 2022" "nsmd Version 1.6.1" "User Commands"
.SH NAME
nsmd \- manual page for nsmd Version 1.6.0
nsmd \- manual page for nsmd Version 1.6.1
.SH DESCRIPTION
nsmd \- Daemon and server for the 'New Session Manager'
.SS "Usage:"


+ 1
- 1
meson.build View File

@@ -24,7 +24,7 @@
project(
'new-session-manager',
'c', 'cpp',
version : '1.6.0',
version : '1.6.1',
license : 'GPLv3',
)



+ 1
- 1
src/nsmd.cpp View File

@@ -69,7 +69,7 @@ static char *daemon_file;
#define NSM_API_VERSION_MAJOR 1
#define NSM_API_VERSION_MINOR 1
#define NSM_API_VERSION_PATCH 2
#define VERSION_STRING "1.6.0"
#define VERSION_STRING "1.6.1"

#define ERR_OK 0
#define ERR_GENERAL_ERROR -1


Loading…
Cancel
Save