From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Sun, 01 Nov 2020 23:34:28 +0100 [thread overview]
Message-ID: <20201101223428.9e6Xn7dCFpRlopCXtIEqtD5X4OJaN84FrffPXhplaUs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25901@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/issues/25901#issuecomment-720162082
Comment:
I've been thinking about this for a while. I don't think anything like the AUR is a good idea, as it exposes void to much of the issues of the AUR and security issues there without much review.
I think there are two reasonable compromises:
1. Adding an alternative secondary void-packages repository that is not confirmed to be working, as no official upstream support for a lack of breakage and is fully community managed. A select group of people accept PRs to this repository, like with void-packages - maybe a different group of people?? Idk, a rough idea.
2. Alternatively, add a page to docs.voidlinux.org containing a list of secondary source and binary package repositories that are "endorsed" by Void for specific wants by users. IDEA: add packages like `void-repo-multilib` like `secondary-repo-ymir` that add repository entries for those that have binary repos.
However, I understand if this doesn't really align with the maintainers and I would see why that is as a contributor.
next prev parent reply other threads:[~2020-11-01 22:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 15:53 [ISSUE] " hippi777
2020-10-27 11:53 ` Duncaen
2020-10-27 11:53 ` Duncaen
2020-10-27 13:20 ` hippi777
2020-10-31 16:58 ` reback00
2020-10-31 17:23 ` hippi777
2020-10-31 17:47 ` reback00
2020-11-01 9:56 ` hippi777
2020-11-01 10:29 ` Duncaen
2020-11-01 11:45 ` hippi777
2020-11-01 12:05 ` Duncaen
2020-11-01 12:06 ` Duncaen
2020-11-01 18:13 ` reback00
2020-11-01 18:14 ` reback00
2020-11-01 18:17 ` reback00
2020-11-01 20:06 ` hippi777
2020-11-01 22:31 ` fosslinux
2020-11-01 22:34 ` fosslinux [this message]
2020-11-02 16:12 ` reback00
2022-04-22 2:14 ` github-actions
2022-04-22 15:56 ` [ISSUE] [CLOSED] " Duncaen
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=20201101223428.9e6Xn7dCFpRlopCXtIEqtD5X4OJaN84FrffPXhplaUs@z \
--to=fosslinux@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).