From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [proposal] templates without official binaries
Date: Fri, 22 Apr 2022 17:56:22 +0200 [thread overview]
Message-ID: <20220422155622.9Ic_BH4um4Ykjzlw_CCotF1MUXh7VMmJIF-PqjnSdn8@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: 1438 bytes --]
Closed issue by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/issues/25901
Description:
hi folks! :)
there are a bunch of rejected stuffs like kernel variants (like libre/xanmod/zen), browsers etc, and the reason against them is basically the compilation time and resources that they consume. (sure, others are rejected cuz of maintenance reasons, and whatever else, but those are different issues for now.)
so actually i think that it would be nice to have a way to give official blessing for some templates that could get enough backers, and that way it wouldnt be necessary to mess with merging the official master with a few other packages, while the need exists for such stuffs, and therefore there would be someone who would put the effort into those...
(also, more or less related, but dropped packages could be moved to somewhere instead of deleting them, so it can be easier to reanimate such, while im not enough deep into git wizardry, and maybe the history can be enough for this one.)
(((the basic idea came from the missing libre kernel, cuz the rest of the system is easy to be kept blob-free, and this holds back much ppl from picking up void, maybe even thats the only missing bit for a respect your freedom cert, and no matter what does that actually mean (as it isnt perfect) its still marginal for many...)))
thx for ur time, and all the bests to all of u folks! :)
prev parent reply other threads:[~2022-04-22 15:56 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
2020-11-02 16:12 ` reback00
2022-04-22 2:14 ` github-actions
2022-04-22 15:56 ` Duncaen [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=20220422155622.9Ic_BH4um4Ykjzlw_CCotF1MUXh7VMmJIF-PqjnSdn8@z \
--to=duncaen@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).