From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: brave-1.2.41-x64
Date: Tue, 29 Sep 2020 02:45:52 +0200 [thread overview]
Message-ID: <20200929004552.JuB_lNhojLH3mBBUfGU_dWU-wvd6wFhzg1cb7TiClQY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18586@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/18586#issuecomment-700358260
Comment:
> @Hoshpak @pullmoll Why don't you consider adding either binary or source package with _restricted=yes_ flag? It works well for _android-studio_ for instance.
See 5511.
> P. S. Honestly, I think we just need a more powerful build server. I'll donate for it, because it seems that build server's capacity is often the main reason to reject many PRs in this repo. See [#5511 (comment)](https://github.com/void-linux/void-packages/pull/5511#issuecomment-699783291) for my opinion about this situation.
#5511 is all the reasons we will not accept Brave. Thank you for linking to it.
> P. P. S. Or maybe we should make something like AUR, but xbps-src based?
No. This is an unsupported idea.
prev parent reply other threads:[~2020-09-29 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:10 [PR PATCH] " voidlinux-github
2020-01-27 16:27 ` voidlinux-github
2020-01-27 16:34 ` voidlinux-github
2020-01-27 16:38 ` voidlinux-github
2020-01-27 18:27 ` [PR PATCH] [Updated] [WIP] " voidlinux-github
2020-01-27 18:34 ` voidlinux-github
2020-01-27 18:35 ` voidlinux-github
2020-01-27 18:37 ` voidlinux-github
2020-01-27 18:38 ` voidlinux-github
2020-01-27 18:40 ` voidlinux-github
2020-01-27 18:41 ` voidlinux-github
2020-01-27 18:52 ` voidlinux-github
2020-01-27 18:53 ` voidlinux-github
2020-01-27 18:56 ` voidlinux-github
2020-01-27 19:02 ` voidlinux-github
2020-01-27 20:28 ` [PR PATCH] [Closed]: " voidlinux-github
2020-09-28 5:49 ` Logarithmus
2020-09-29 0:45 ` Vaelatern [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=20200929004552.JuB_lNhojLH3mBBUfGU_dWU-wvd6wFhzg1cb7TiClQY@z \
--to=vaelatern@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).