From: paoloschi <paoloschi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Worker file manager
Date: Wed, 30 Aug 2023 20:28:26 +0200 [thread overview]
Message-ID: <20230830182826.UvmDZojHUwnoz7x7itRJibPR3TGldNcgNLLRs_eXm90@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45711@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
New comment by paoloschi on void-packages repository
https://github.com/void-linux/void-packages/issues/45711#issuecomment-1699630910
Comment:
Today I subscribed to the _Workerfm-users_ mailing list and mentioned dBus messages in the terminal.
I received this single reply at the time:
> hi,
>
> as a user:
>
> if compiling worker there's an option to remove dbus support:
> ./configure --without-dbus
>
> there are other options see
> ./configure --help
>
>
> if removing dbus & hal some drives/flash drives removable media aren't
> updated as often in the volume manager, yet it is quite usable anyway,
> since there a trigger to "update list" in the volume manager.
> the volume manager displays a list of mount points, I don't know how
> yet it works.
> related packages hal and udisk2 packages are not required, can
> be uninstalled.
>
> in the config window there's an entry :
> experts settings > Volume manager settings
> it could matter to adapt some the config there to get it to do its
> things.
>
>
> have a great day,
> rno
> noospot.dynv6.net
next prev parent reply other threads:[~2023-08-30 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 14:40 [ISSUE] " paoloschi
2023-08-29 2:40 ` mtboehlke
2023-08-29 9:38 ` paoloschi
2023-08-29 20:53 ` mtboehlke
2023-08-30 7:23 ` paoloschi
2023-08-30 18:28 ` paoloschi [this message]
2023-12-23 9:17 ` paoloschi
2023-12-23 21:44 ` mtboehlke
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=20230830182826.UvmDZojHUwnoz7x7itRJibPR3TGldNcgNLLRs_eXm90@z \
--to=paoloschi@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).