Package Details: thelounge 4.2.0-2

Git Clone URL: (read-only, click to copy)
Package Base: thelounge
Description: Modern self-hosted web IRC client
Upstream URL:
Licenses: MIT
Submitter: Max-P
Maintainer: Max-P (S13ntist)
Last Packager: S13ntist
Votes: 17
Popularity: 0.079629
First Submitted: 2016-02-12 23:03
Last Updated: 2020-08-20 16:46

Latest Comments

1 2 Next › Last »

S13ntist commented on 2020-06-19 20:56

@starquake please don't I'll just close it for exactly the same reason as was already mentioned.

starquake commented on 2020-06-19 18:34

I will! Thanks!

Max-P commented on 2020-06-19 18:28

@starquake Yeah it's wrong but the package is officially maintained by the upstream developers and they're super dense about it being identical across distros, so that the documentation on the website is correct no matter what installation method is used. It's heavily based around what you'd get with npm install -g (eww).

Feel free to complain on GitHub:

starquake commented on 2020-06-19 18:17

I'm using etckeeper and right now it's backing up log files of thelounge. This wouldn't be the case if it was set up like @Celti mentions.

Are you considering this?

Celti commented on 2019-11-30 07:26

There's precedent in other packages (various things that install to /usr/share/webapps come to mind) to use the sensible install location, then move the configuration to /etc and symlink to that from where the application expects it; e.g., /var/lib/thelounge/config.js -> /etc/thelounge/config.js.

angelsl commented on 2019-07-29 08:34


I could dump everything to /var but that just means that now the configs are in the wrong place.

There are packages whose configuration files live in /var too because they are together with the data. E.g. postgres.

S13ntist commented on 2019-04-15 15:55

@Lucki it's both actually, config and data. I proposed to split the two directories from each other, but that involved some hackery with symlinks as upstream doesn't support it.

I could dump everything to /var but that just means that now the configs are in the wrong place.

meaning won't fix, works as designed

Lucki commented on 2019-04-15 12:24

Right now the complete home folder is set to /etc/thelounge. According to the guidelines this would probably better be placed in /var/lib/thelounge/ as that folder is for persistent application storage?

Max-P commented on 2018-02-21 02:39

@xogium I run a test build before committing, but I've just tried it again and it seems to work for me (pardon the french):

The line that errors for you is: grep -FRlZ "$startdir" "$pkgdir" | \ xargs -0 -- sed -i "s|$startdir|/tmp/build|g"

Which is there to remove references to the build directory from the sources. That means for some reason the build process didn't leave the build path in for you so nothing ends up passed to sed. You can safely remove that line from the PKGBUILD and it should build.

xogium commented on 2018-02-21 02:29

It appeares the build is failing for me for v2.7. I tried with aurutils-git and with makepkg itself, manually:

uws@9.14.0 install /build/thelounge/pkg/thelounge/usr/lib/node_modules/thelounge/node_modules/uws node-gyp rebuild > build_log.txt 2>&1 || exit 0 + thelounge@2.7.1 added 236 packages in 10.084s sed: no input files ==> ERROR: A failure occurred in package(). Aborting...

Is anyone else having this issue ? Thanks