From: costowell <costowell@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Add discover and PackageKit-qt
Date: Fri, 30 Dec 2022 08:30:52 +0100 [thread overview]
Message-ID: <20221230073052.1w2LXyUdUJAbZ2-rNcBBgwDQLrKgzqEsXI2x9fW7WPs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41359@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by costowell on void-packages repository
https://github.com/void-linux/void-packages/pull/41359#issuecomment-1367771505
Comment:
I would like to support flatpaks and firmware updating maybe? (See screenshot) I'm not exactly sure if by compiling discover with support for flatpaks and fwupd that it will also force them to be dependencies. Ideally we get them on there for people that like all of these software/firmware tools in one thing.
next prev parent reply other threads:[~2022-12-30 7:30 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 7:18 [PR PATCH] " costowell
2022-12-30 7:23 ` costowell
2022-12-30 7:30 ` costowell [this message]
2022-12-30 7:31 ` costowell
2022-12-30 7:33 ` costowell
2022-12-30 19:59 ` [PR PATCH] [Updated] " costowell
2022-12-30 20:08 ` [PR REVIEW] " classabbyamp
2022-12-30 20:08 ` classabbyamp
2022-12-30 20:08 ` classabbyamp
2022-12-30 20:08 ` classabbyamp
2022-12-30 20:08 ` classabbyamp
2022-12-30 20:09 ` costowell
2022-12-30 20:10 ` costowell
2022-12-30 20:11 ` classabbyamp
2022-12-30 20:11 ` costowell
2022-12-30 20:11 ` classabbyamp
2022-12-30 20:11 ` classabbyamp
2022-12-30 20:40 ` [PR PATCH] [Updated] " costowell
2022-12-30 20:44 ` costowell
2022-12-30 20:44 ` costowell
2022-12-30 20:50 ` classabbyamp
2022-12-30 21:40 ` [PR PATCH] [Updated] " costowell
2022-12-30 21:43 ` costowell
2022-12-30 22:54 ` costowell
2022-12-31 18:10 ` Add PackageKit support to void costowell
2022-12-31 18:11 ` classabbyamp
2022-12-31 18:25 ` costowell
2022-12-31 18:30 ` classabbyamp
2023-01-01 3:03 ` oreo639
2023-01-01 3:04 ` oreo639
2023-01-01 3:19 ` oreo639
2023-01-01 5:46 ` classabbyamp
2023-01-02 19:52 ` [PR PATCH] [Updated] " costowell
2023-01-02 19:58 ` costowell
2023-01-02 20:57 ` costowell
2023-01-02 23:45 ` costowell
2023-01-03 0:27 ` costowell
2023-01-03 19:51 ` costowell
2023-01-05 17:59 ` [PR PATCH] [Updated] " costowell
2023-01-05 20:43 ` costowell
2023-01-07 14:14 ` [PR REVIEW] " classabbyamp
2023-01-07 17:47 ` [PR PATCH] [Updated] " costowell
2023-01-15 6:25 ` costowell
2023-01-15 6:29 ` classabbyamp
2023-01-15 6:31 ` [PR PATCH] [Updated] " costowell
2023-01-15 6:36 ` costowell
2023-01-15 6:36 ` costowell
2023-01-15 6:39 ` classabbyamp
2023-01-15 7:30 ` [PR PATCH] [Updated] " costowell
2023-01-15 7:41 ` costowell
2023-01-15 7:46 ` costowell
2023-01-15 7:48 ` costowell
2023-01-15 17:44 ` costowell
2023-01-15 17:44 ` costowell
2023-01-15 17:48 ` classabbyamp
2023-01-15 17:49 ` costowell
2023-01-15 18:04 ` classabbyamp
2023-01-15 18:48 ` [PR PATCH] [Updated] " costowell
2023-01-15 19:33 ` classabbyamp
2023-01-15 19:35 ` [PR PATCH] [Updated] " costowell
2023-01-15 21:17 ` costowell
2023-01-15 22:09 ` costowell
2023-01-15 22:13 ` costowell
2023-01-15 22:27 ` [PR PATCH] [Updated] " costowell
2023-04-16 1:56 ` github-actions
2023-04-16 16:03 ` zen0bit
2023-07-16 2:13 ` github-actions
2023-07-31 1:52 ` [PR PATCH] [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=20221230073052.1w2LXyUdUJAbZ2-rNcBBgwDQLrKgzqEsXI2x9fW7WPs@z \
--to=costowell@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).