Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Packages with systemd cruft
Date: Fri, 23 Jul 2021 15:12:13 +0200	[thread overview]
Message-ID: <20210723131213.1brQrMW7auS710D6EyMTwEiPcRzRONgbEfnzbgr2w8s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32154@inbox.vuxu.org>

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

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/32154#issuecomment-885628562

Comment:
> We had a small discussion on IRC whether this should/could be already solved in `xbps-src` by excluding default systemd paths from package contents like `/usr/lib/systemd` and `/usr/share/dbus-1/services`.

dbus services != systemd services, only /usr/lib/systemd should be always removed

> Part 2:

Most of these are dbus services which are irrelevant, other services are in the documentation which is not harmful in any way and others are already in the original post. When you filter them out, you will have only a few files in part 2.

  parent reply	other threads:[~2021-07-23 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 10:24 [ISSUE] " Anachron
2021-07-23 11:05 ` paper42
2021-07-23 11:39 ` leahneukirchen
2021-07-23 12:24 ` Anachron
2021-07-23 12:35 ` Anachron
2021-07-23 12:36 ` Anachron
2021-07-23 12:37 ` Anachron
2021-07-23 12:40 ` Anachron
2021-07-23 12:41 ` Anachron
2021-07-23 13:12 ` paper42 [this message]
2021-07-23 16:01 ` Duncaen
2021-07-23 16:02 ` Duncaen
2021-07-23 16:02 ` Duncaen
2021-07-23 16:03 ` Duncaen
2021-07-23 16:57 ` Anachron
2021-07-24  5:52 ` Anachron
2021-07-24  5:53 ` Anachron
2022-05-30  2:15 ` github-actions
2022-06-14  2:13 ` [ISSUE] [CLOSED] " github-actions

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=20210723131213.1brQrMW7auS710D6EyMTwEiPcRzRONgbEfnzbgr2w8s@z \
    --to=paper42@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).