Queue download if update asked per ID

The version of the update function is chosen depending on the URI that is passed to the update method of the repo module:

• An ID URI: the ___worker_update_from_ids is selected, the user will be able to queue the different kara to download by calling again the update method with others ID URI
• Anything else: the ___worker_update is selected. It will download all the database from Kurisu, filtering if the passed URI is not URI_NULL.

The aim here is to offer a download process option which permit the user of doing a simple dry-update and then selecting the different karas he wants to download id per id.

Will close #102 (closed) for now.

Also close some TODOs.

README.md

@@ -59,7 +59,8 @@ The manual way of installing and setting up lektor:
 ```sh
 cmake -Bbuild \
     -DCMAKE_C_COMPILER=clang           \ # Choose the compiler
-    -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=Debug # The debug stuff
+    -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ # For clangd/ccls
+    -DCMAKE_BUILD_TYPE=Debug             # The debug stuff
 ```
 
 Note that the last option is here to generate the `compile_commands.json`, you
@@ -68,7 +69,9 @@ should copy it at the root of the project.
 The sqlite database and the config file will be created automatically if needed,
 i.e. on the first run. If you are upgrading lektor, the config might not be
 correct. You can delete the config file or use the `lkt admin config` to
-generate the config file again.
+generate the config file again. If you are using special modules or are
+compiling lektor without static modules, you may set their **absolute path**
+inside the lektor's config file.
 
 > **Important note**: Upgrading the config or the database scheme automatically
 is not supported yet. If you are experiencing weird things with lektord, please
@@ -76,9 +79,6 @@ try first to delete the database and config and regenerate them. There are
 currently no way of doing a backup of playlists and stickers with lektor, this
 is WIP.
 
-If you are using special modules or are compiling lektor without static modules,
-you may set their **absolute path** inside the lektor's config file.
-
 ## Preparing a kara for lektor
 
 The ideal way of populating lektor is using *Kurisu*. The `update` is here for
@@ -92,15 +92,12 @@ command.
 To run lektor, you can simply run the binary like: `./lektord`. If lektord did
 not exited normally (i.e. without the `lkt adm kill` command), the database will
 still store the fact that lektord is running. To by-pass it, you will need to
-launch lektord with the `-F` (forced) option, like `lektord -F`.
-
-It is not recommended to launch always lektord with the `-F` option, because
-that way you could launch multiple instances of the lektod daemon, which could
-results in undefined behaviours.
-
-Lektor will use specialized software (hwdec set to yes), if you have an nvidia
-card with optimus (in almose every laptop), please use `optirun` or `primusrun`:
-`optirun ./lektord`
+launch lektord with the `-F` (forced) option, like `lektord -F`. It is not
+recommended to launch always lektord with the `-F` option, because that way you
+could launch multiple instances of the lektod daemon, which could results in
+undefined behaviours. Lektor will use specialized software (hwdec set to yes),
+if you have an nvidia card with optimus (in almose every laptop), please use
+`optirun` or `primusrun`: `optirun ./lektord`
 
 ### How to update the lektord database
 
@@ -142,6 +139,6 @@ Please, refer to the [CONTRIBUTING](CONTRIBUTING.md) file.
 ## MPD
 
 Lektor is almost MPD compatible, at least it uses the same protocol, which can
-be consulted [here](https://www.musicpd.org/doc/html/protocol.html#). The full
-support for MPD clients (like mpc and ncmpc) is still WIP. For the MPD
+be consulted [here](https://mpd.readthedocs.io/en/stable/protocol.html). The
+full support for MPD clients (like mpc and ncmpc) is still WIP. For the MPD
 compatibility list, see the [CONTRIBUTING](CONTRIBUTING.md) file.