Skip to content

version 1.4.0
Compare
Choose a tag to compare
@neogeographica neogeographica released this 16 Feb 20:07
· 20 commits to main since this release
v1.4.0
b2c1742

As with all the "releases", this is just marking a certain point in the state of the repo. To make use of this, you can download a .zip or .tar.gz archive of the repo using the asset links below. (And then start with the toplevel readme.)

If you're starting from scratch with this version, well the docs have been updated accordingly so you'll be fine. If you're using the previous version and want to migrate... I'll describe the migration steps in a minute, but the rationale for them is clearer if we talk about the changes first. So let's do that!

  • One of the most obvious changes is that "quakelaunch.conf" will no longer sit next to your "quakelaunch" script; instead it will be stored according to XDG config-file placement rules. (Normally this means it will be in the "~/.config/quakelaunch" directory.)
  • A "quakelaunch-defaults.conf" file will be autogenerated in that same location, containing the defaults for all the properties which can be set in "quakelaunch.conf".
  • There's no longer a separate "quakecleanup" script. That functionality is now handled by the main "quakelaunch" script. The quakecleanup.desktop file has changed accordingly.
  • Documentation now directs putting "quakelaunch" in your PATH, so that the .desktop files no longer need to specify an explicit path for it.
  • The MIME type definition for Quake .bsp files now uses the file header rather than file extension to identify them. This should avoid any conflict with other uses of the .bsp extension.
  • FYI a new "manifest v3" version of the Chrome extension is available in the repo, in a directory next to the current ("manifest v2") version. However, it is recommended to stick with the current one for now. (Eventually Google/Chrome will force us to switch to the new one.)
  • And there's various documentation updates about the above changes, as well as a rework of how the docs describe the way the browser extension works.

OK, here's what migration of an existing setup would involve.

First, apply the new version of the the Quake .bsp file MIME type:

xdg-mime install --novendor --mode user x-bsp-map.xml
update-mime-database ~/.local/share/mime

Next:

  • Remove your installed "quakecleanup" script.
  • Replace your installed "quakelaunch" script with the new one.

Now manually run the new installed "quakelaunch" script once, without arguments, just to import your current "quakelaunch.conf". (You can immediately quit out of Quake when it launches.) In the shell where you ran "quakelaunch", you'll see an info message about where your "quakelaunch.conf" now lives.

If the installed "quakelaunch" script isn't in your PATH, you may choose to move it into some PATH directory at this point. (I'd recommend doing so if possible.)

Before making any .desktop file changes, take note of whatever modifications you previously made to the installed .desktop files. Probably if you made any changes, it was only to set the Icon path value in "quake.desktop", and maybe also setting the Exec path values in one or both of the .desktop files.

Check out the new .desktop files here and see if you need/want to apply those same changes. E.g. maybe you need to set the Icon path in "quake.desktop". And if the installed quakelaunch script is not in your PATH, modify the Exec value in both "quake.desktop" and "quakecleanup.desktop" to specify the complete correct path to "quakelaunch".

OK, now you can apply the new versions of the .desktop files:

xdg-desktop-menu install --novendor --mode user quake.desktop
xdg-desktop-menu install --novendor --mode user quakecleanup.desktop
xdg-mime default quake.desktop application/x-quake
xdg-mime default quake.desktop application/x-bsp-map
xdg-mime default quake.desktop application/x-qz
update-desktop-database ~/.local/share/applications

No migration needed for the browser extension, since the current version hasn't changed. As mentioned in the relevant readme, I don't generally recommend switching to the "manifest v3" version yet.

I'll insert my standard apology here for not having a cleaner process for installation or upgrade/migration, but I'm pretty dubious that there are many (if any) folks other than me that are using this. :-)

Assets 2
Loading