From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: xdg-desktop-portal: include a default portals.conf
Date: Thu, 05 Oct 2023 18:52:21 +0200 [thread overview]
Message-ID: <20231005165221.nSiKAiFHabme2f4-hfqQJfeAv6evrPmRydEXhE-Ljcc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46449@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
There's a merged pull request on the void-packages repository
xdg-desktop-portal: include a default portals.conf
https://github.com/void-linux/void-packages/pull/46449
Description:
Without this, `xdg-desktop-portal` cannot do anything as of 1.18.0. DEs and WMs should probably ship their own if they want to use a specific frontend, but this should be good enough for now.
This conf file is put in the lowest precedence location, and generic `portals.conf` is overriden if `XDG_CURRENT_DESKTOP-portals.conf` is found, so this should be fairly safe.
Additionally, this `portals.conf` does not require any specific frontend, just the special value `*`, which means the first one found in lexicographical order.
See [portals.conf(5)](https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst) for more details. This manpage is also installed now by adding `python3-docutils` to `hostmakedepends`.
fixes #46317
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
prev parent reply other threads:[~2023-10-05 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 16:28 [PR PATCH] " classabbyamp
2023-10-05 16:29 ` [PR PATCH] [Updated] " classabbyamp
2023-10-05 16:52 ` classabbyamp [this message]
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=20231005165221.nSiKAiFHabme2f4-hfqQJfeAv6evrPmRydEXhE-Ljcc@z \
--to=classabbyamp@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).