Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [feedback request] drop icecat
Date: Wed, 27 Jan 2021 04:37:37 +0100	[thread overview]
Message-ID: <20210127033737.D0wljKHNuNIjklBozo6f_ND1teTs-kQcCn3OZc5kFp4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27731@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/27731#issuecomment-767998895

Comment:
"Restricted" means Void is, well, restricted from distributing the package contents. It is not a mechanism to provide templates we just don't care to build.

A key reason for not allowing other browsers is their excessive build time. That doesn't mean it's the only reason. Restricted packages tend to rot faster than regular packages because the tooling that ensures consistency of the repository is (necessarily) unaware of restricted packages, so we can't track potential breakage when we update other packages.

  parent reply	other threads:[~2021-01-27  3:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  5:31 [ISSUE] " q66
2021-01-07  6:17 ` Vaelatern
2021-01-07  6:20 ` the-maldridge
2021-01-07  6:46 ` pullmoll
2021-01-07  6:48 ` pullmoll
2021-01-07  6:48 ` the-maldridge
2021-01-07  6:51 ` pullmoll
2021-01-07  6:52 ` the-maldridge
2021-01-07 13:52 ` ericonr
2021-01-07 14:00 ` q66
2021-01-07 19:43 ` uzr123x
2021-01-10 23:43 ` tibequadorian
2021-01-10 23:44 ` tibequadorian
2021-01-11  9:12 ` travankor
2021-01-11  9:24 ` the-maldridge
2021-01-11  9:24 ` [ISSUE] [CLOSED] " the-maldridge
2021-01-11  9:32 ` pullmoll
2021-01-11  9:33 ` pullmoll
2021-01-11  9:34 ` the-maldridge
2021-01-11 12:57 ` q66
2021-01-19 10:00 ` uber97
2021-01-19 10:01 ` the-maldridge
2021-01-27  2:14 ` tarkov2213
2021-01-27  2:16 ` the-maldridge
2021-01-27  3:08 ` tarkov2213
2021-01-27  3:09 ` tarkov2213
2021-01-27  3:11 ` tarkov2213
2021-01-27  3:37 ` ahesford [this message]
2021-01-27  4:10 ` tarkov2213
2021-01-27  4:15 ` tarkov2213
2021-01-27  4:17 ` ahesford
2021-01-27 13:01 ` tibequadorian
2021-01-27 13:07 ` tibequadorian
2021-01-27 13:15 ` Gottox
2021-01-27 17:51 ` ericonr
2021-01-27 17:53 ` [ISSUE] [CLOSED] " pullmoll
2021-01-27 18:38 ` q66
2021-02-01 17:48 ` Raffadiely
2021-02-01 17:48 ` Raffadiely

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=20210127033737.D0wljKHNuNIjklBozo6f_ND1teTs-kQcCn3OZc5kFp4@z \
    --to=ahesford@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).