Github messages for voidlinux
 help / color / mirror / Atom feed
From: hfel <hfel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Brave
Date: Thu, 21 May 2020 17:42:32 +0200	[thread overview]
Message-ID: <20200521154232.7OXJDcMwe_Kzn0oV3N_ZhaCIG9OkuuLfiiL54wIDk_o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5444@inbox.vuxu.org>

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

New comment by hfel on void-packages repository

https://github.com/void-linux/void-packages/issues/5444#issuecomment-632164652

Comment:
> There is no point in replacing, this is not about size of the resulting package.
> 
> The objections are more about brave being another chromium fork, meaning it requires heavy patching, maintenance and hours of compile time.

Can you explain to the technically illiterate in this matter why being a chromium fork which one would presume is still released by the relevant developers in a form where all the necessary components are present requires more maintenance than non-forks-of-chromium?

  parent reply	other threads:[~2020-05-21 15:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5444@inbox.vuxu.org>
2020-01-26 19:04 ` voidlinux-github
2020-01-27  2:15 ` voidlinux-github
2020-01-27  6:10 ` voidlinux-github
2020-01-27  6:37 ` voidlinux-github
2020-01-30  1:19 ` voidlinux-github
2020-04-04  2:05 ` anjandev
2020-04-04  2:07 ` the-maldridge
2020-04-04  2:10 ` anjandev
2020-04-04  2:11 ` anjandev
2020-04-04  2:11 ` anjandev
2020-04-04  2:12 ` anjandev
2020-04-04  2:17 ` anjandev
2020-04-04  2:17 ` the-maldridge
2020-04-04  2:18 ` anjandev
2020-04-04  2:18 ` anjandev
2020-04-04  2:19 ` anjandev
2020-05-21  8:49 ` gspe
2020-05-21  9:25 ` Duncaen
2020-05-21 15:40 ` hfel
2020-05-21 15:42 ` hfel [this message]
2020-05-21 15:49 ` the-maldridge
2020-05-21 15:51 ` Duncaen
2020-05-21 15:54 ` Duncaen
2020-05-21 16:13 ` hfel
2020-05-21 16:23 ` Duncaen
2020-10-04  0:36 ` the-maldridge
2020-10-04  0:36 ` [ISSUE] [CLOSED] " the-maldridge
2020-10-04 22:23 ` unihernandez22
2020-10-05  5:08 ` Anachron
2020-10-16 20:12 ` unihernandez22
2020-10-16 20:36 ` q66
2020-11-05 21:28 ` Logarithmus
2020-11-05 21:31 ` Logarithmus
2020-11-05 21:34 ` Logarithmus
2020-11-05 21:34 ` Logarithmus
2020-11-05 21:43 ` Duncaen
2020-11-05 21:43 ` Duncaen
2020-11-06 15:31 ` unihernandez22
2020-11-06 15:34 ` unihernandez22
2020-11-06 15:35 ` Duncaen
2021-11-22  8:22 ` Animeshz
2021-11-22  8:29 ` Animeshz

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=20200521154232.7OXJDcMwe_Kzn0oV3N_ZhaCIG9OkuuLfiiL54wIDk_o@z \
    --to=hfel@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).