Package Details: loot 0.16.0-3

Git Clone URL: https://aur.archlinux.org/loot.git (read-only, click to copy)
Package Base: loot
Description: A load order optimisation tool for the Elder Scrolls (Morrowind and later) and Fallout (3 and later) games.
Upstream URL: https://loot.github.io
Licenses: GPL3
Submitter: gargan
Maintainer: gargan (C0rn3j)
Last Packager: C0rn3j
Votes: 3
Popularity: 1.21
First Submitted: 2019-10-24 01:46
Last Updated: 2021-04-07 16:46

Latest Comments

C0rn3j commented on 2021-04-04 15:42

I have updated the package to current stable, fixed the node downloads (seems like yarn install wasn't running for both loot and libloot, not sure if the fix is kosher but it works) and added the required replacement for Spotify's CEF until the next version drops.

@Neko-san

it fails near the end of compilation

That's because Spotify changed their infrastructure in 2021-01 and current stable LOOT is from 2020, so compiling stable broke in 2021.

Really wish Bethesda mod tools were more supported in Linux

You can always compile git loot, see here:
https://github.com/loot/loot/pull/1162#issuecomment-545120145

Neko-san commented on 2021-02-18 06:03

@abelian424 This almost worked for me with the now latest version(s) (Loot v0.16 & libloot v0.16.2)

However, it fails near the end of compilation

Really wish Bethesda mod tools were more supported in Linux, it's painful...

abelian424 commented on 2020-01-01 13:58

Editing the pkgfile works fine for installing the latest version of loot (0.15.1 at the time). Just edit the pkgver and _pkglibver entries to the latest version. Update the sha256sum for each and edit out the patch references under prepare(). The build will fail because npm does not download all dependencies automatically. I used npm-accel within the makepkg directory for loot to populate the node_versions folder and the package compiled successfully.

katt commented on 2019-12-18 14:00

Shouldn't libloot and loot be two different packages instead of merged like this?