3 The general procedure is:
5 * stop the old daemon, e.g. with
6 /etc/init.d/disorder stop
7 * back up your database
8 * build and install the new version as described in the README
9 * update the configuration files (see below)
10 * start the new daemon, e.g. with
11 /etc/init.d/disorder start
13 The rest of this file describes things you must pay attention to when
14 upgrading between particular versions. Minor versions are not
15 explicitly mentioned; a version number like 1.1 implicitly includes
22 The first thing the server does when upgrading from 1.5 is run the
23 disorder-dbupgrade program. This is necessary to modify any non-ASCII track
24 names to meet the latest version's stricter normalization practices. The
25 upgrade should succeed automatically; if not it should leave an error message
28 It is strongly recommended that you back up your database before performing the
29 upgrade. For example, as root, with the server STOPPED:
34 To restore, again as root:
39 ** 'transform' and 'namepart' directives
41 'transform' has moved from the web options to the main configuration file, so
42 that they can be used by other interfaces. The syntax and semantics are
45 More importantly however both 'transform' and 'namepart' are now optional, with
46 sensible defaults being built in. So if you were already using the default
47 values you can just delete all instances of both.
49 ** enabled' and 'random_enabled' directives
51 These have been removed. Instead the state persists from one run of the server
56 ** Raw Format Decoders
58 You will probably want reconfigure your install to use the new facilities
59 (although the old way works fine). See the example configuration file and
60 README.raw for more details.
62 Depending on how your system is configured you may need to link the disorder
63 libao driver into the right directory:
65 ln -s /usr/local/lib/ao/plugins-2/libdisorder.so /usr/lib/ao/plugins-2/.
71 It is important that $sbindir is on the server's path. The example init script
72 guarantees this. You may need to modify the installed one. You will get
73 "deadlock manager unexpectedly terminated" if you get this wrong.
75 ** namepart directives
77 These have changed in three ways.
79 Firstly they have changed to substitute in a more convenient way. Instead of
80 matches for the regexp being substituted back into the original track name, the
81 replacement string now completely replaces it. Given the usual uses of
82 namepart, this is much more convenient. If you've stuck with the defaults no
83 changes should be needed for this.
85 Secondly they are matched against the track name with the collection root
88 Finally you will need to add an extra line to your config file as follows for
89 the new track aliasing mechanisms to work properly:
91 namepart ext "(\\.[a-zA-Z0-9]+)$" "$1" *
95 ** Web Interface Changes
97 The web interface now includes static content as well as templates.
98 The static content must be given a name visible to HTTP clients which
99 maps to its location in the real filesystem.
101 The README suggests using a rule in httpd.conf to make /static in the
102 HTTP namespace point to /usr/local/share/disorder/static, which is
103 where DisOrder installs its static content (by default).
104 Alternatively you can set the url.static label to the base URL of the
107 ** Configuration File Changes
109 The trackname-part web interface directive has now gone, and the
110 options.trackname file with it.
112 It is replaced by a new namepart directive in the main configuration
113 file. This has exactly the same syntax as trackname-part, only the
114 name and location have changed.
116 The reason for the change is to allow track name parsing to be
117 centrally configured, rather than every interface to DisOrder having
118 to implement it locally.
120 If you do not install new namepart directives into the main
121 configuration file then track titles will show up blank.
123 If you do not remove the trackname-part directives from the web
124 interface configuration then you will get error messages in the web