Package Details: appimagelauncher-git r1251.71e8e32-1

Git Clone URL: https://aur.archlinux.org/appimagelauncher-git.git (read-only, click to copy)
Package Base: appimagelauncher-git
Description: A Helper application for running and integrating AppImages.
Upstream URL: https://assassinate-you.net/tags/appimagelauncher/
Keywords: appimage
Licenses: MIT
Conflicts: appimagelauncher
Provides: appimagelauncher
Submitter: AJSlye
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 4
Popularity: 0.000001
First Submitted: 2018-04-24 14:08 (UTC)
Last Updated: 2023-06-11 07:52 (UTC)

Pinned Comments

FabioLolix commented on 2023-11-29 22:43 (UTC)

There is an issue open since June https://github.com/TheAssassin/AppImageLauncher/issues/574


I would recommend to use a VM of a base arch install and check what dependencies are missing using that.

We have devtools for building in a clean chroot https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot, typically I do both a clean build and a dirty build but the program is broken now

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

<deleted-account> commented on 2019-09-09 14:58 (UTC)

V new to arch/builds, but thank you for response, and link ... have looked at that, but can't match up the lines 56-66 or see how to apply fix (looking in pamac/build files).

AJSlye commented on 2019-09-09 13:18 (UTC) (edited on 2019-09-09 13:27 (UTC) by AJSlye)

Dependencies need to be made (aka make -j) before cmake to resolve path limitations in cmake, then make needs to be run again after to finish compile.

Example:

build() {

cd "$srcdir/$_pkgname"

make -j

cmake . \

    -DCMAKE_INSTALL_PREFIX=/usr/ \   
    -DCMAKE_INSTALL_LIBDIR=lib \   
    -DUSE_SYSTEM_GTEST=ON \   
    -DUSE_SYSTEM_XZ=ON \   
    -DUSE_SYSTEM_LIBARCHIVE=ON \   
    -DBUILD_TESTING=OFF

make -j

}

Reference: https://github.com/TheAssassin/AppImageLauncher/issues/237

<deleted-account> commented on 2019-09-09 12:43 (UTC)

/usr/bin/AppImageLauncher: error while loading shared libraries: libappimageupdate.so: cannot open shared object file: No such file or directory

did the solution below, re /usr/lib/systemd/user/appimagelauncherfs.service alterations. Unfortunately no change. Accessing appimagelauncher settings crashes too. Tried both appimagelauncher and git.

AJSlye commented on 2019-05-04 14:58 (UTC) (edited on 2019-05-04 15:01 (UTC) by AJSlye)

Appimages are meant to be mounted at application launch.

Why would you mount them at boot?

That would add system overhead with many duplicate libraries, etc., permanently loaded into ram.

FirstAirBender commented on 2019-05-04 05:24 (UTC) (edited on 2019-05-04 05:25 (UTC) by FirstAirBender)

On ArcoLinux had to change the /usr/lib/systemd/user/appimagelauncherfs.service to:

[Unit]
Description=AppImageLauncherFS daemon
Before=display-manager.service

[Service]
Type=simple
ExecStart=/usr/bin/appimagelauncherfs
Restart=always
RestartSec=2

[Install]
WantedBy=default.target

Now the app images are mounted at boot

AJSlye commented on 2019-04-11 14:47 (UTC) (edited on 2019-04-11 14:52 (UTC) by AJSlye)

This is a coninuous release project, the version is updated at build time.

I'm not the main maintainer, TheAssasin is, I don't have access to orphan this.

Oberon, are you also maintaining the Manjaro package now?

I'm only asking because, it also needs to be updated.

oberon2007 commented on 2019-04-11 11:16 (UTC)

AJ I am now maintaining the stable release pkg. If you want to orphan the git version I can adopt it, too.

AJSlye commented on 2019-02-03 00:13 (UTC) (edited on 2019-02-03 00:16 (UTC) by AJSlye)

There is no xdd package, this is arch. Besides, neovim-drop-in should satisfy the vim dependency.

ConfuZzled commented on 2019-02-02 23:11 (UTC)

The dependencies should be changed so that it doesn't depend on vim, but rather on xdd, since that's what's actually required by the package. Just depending on vim causes build problems when other AUR packages like neovim-drop-in are installed

AJSlye commented on 2019-01-19 20:15 (UTC) (edited on 2019-01-19 20:16 (UTC) by AJSlye)

I no longer have a need to maintain this myself, Manjaro has taken over maintaining this package in their own repositories.

Please, make all future inquiries to TheAssassin as he is the developer.