Github messages for voidlinux
 help / color / mirror / Atom feed
From: m4rcu5 <m4rcu5@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: AppImageLauncher
Date: Thu, 04 Feb 2021 16:05:21 +0100	[thread overview]
Message-ID: <20210204150521.gRXRpmneETeyqkYdeeMJ3sEh6AZVzFcO6zXlk7VN4uk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26702@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

New comment by m4rcu5 on void-packages repository

https://github.com/void-linux/void-packages/issues/26702#issuecomment-773376739

Comment:
Hi,

I took a stab at it in this https://github.com/m4rcu5/void-packages/commit/1bce018577ac5bbb7fe6bd84c4cb83225e2f76ff commit.

It's not pretty as the package has some hard dependencies on systemd. It uses that for managing the user services `appimagelauncherd`. To get around this I disabled the daemon controls in the GUI and added a note to the end user, to take care of this themself.

![image](https://user-images.githubusercontent.com/219754/106911572-973ec180-6702-11eb-977f-9c1f5e9e9e6e.png)


First-time Void package builder here, so recommendations and improvements are welcome.

The package itself seems to work as intended on my machines, if you manage the daemon yourself.

  reply	other threads:[~2021-02-04 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 19:48 [ISSUE] " cwross
2021-02-04 15:05 ` m4rcu5 [this message]
2021-03-24  2:45 ` JJGadgets
2021-03-24 13:38 ` m4rcu5
2021-03-25  1:16 ` JJGadgets
2021-11-12  9:06 ` Thomashighbaugh
2022-02-22 18:07 [ISSUE] " distefam
2022-02-22 20:56 ` notthewave

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210204150521.gRXRpmneETeyqkYdeeMJ3sEh6AZVzFcO6zXlk7VN4uk@z \
    --to=m4rcu5@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).