From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Sun, 01 Nov 2020 19:17:21 +0100 [thread overview]
Message-ID: <20201101181721.N3YP8VNNATKx6X0KooqwmKKrnTiCi_ZjM5H7qTAjHnU@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: 2091 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/issues/25901#issuecomment-720129719
Comment:
@Duncaen
> They didn't follow our commit title rules so you have to look at commits like "Update" and "fix scripts" to find out what they actually changed.
We didn't plan for merging with upstream. Maybe that's our bad. But we didn't think it's ever going to be merged with upstream, at least not like it's done currently. The templates are directly changed on their place, which is designed for a full libre experience, replacing their nonfree versions. We thought Void will never accept that. So we didn't follow those rules.
If Void ever decides to introduce a libre repo, those commits will not be used. Instead changes will have to be made separately (for the libre repo packages). So I guess this should be fine. But let us know if you think otherwise.
> My position is that we don't want to maintain more patches than necessary, adding your patches for liberation (which no one of the void maintainers care about) just adds more work for everyone.
I hope that more Void maintainers will be interested in future to get at least some form of libre experience into Void. This is not only important for user freedom but sometimes important for security and privacy as well. Purism and others are working towards a libre environment. I hope maintainers understand what it brings for the community.
> the original proposal here, is for having templates for whatever stuffs that arent built officially. u can even think about it as a junkyard, where ppl can find their own treasures, that they will maybe need to work on (or maybe not)
btw... is this happening? This will be a blessing since I heard many complaining that there aren't enough packages on official repos. If there is a separate repo for user packages they can be found in one place rather than being scattered throughout the web.
They won't have to go through build process. But to be manually built by users, just like AUR.
Edit: uppercase, build process
next prev parent reply other threads:[~2020-11-01 18:17 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 [this message]
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 ` [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=20201101181721.N3YP8VNNATKx6X0KooqwmKKrnTiCi_ZjM5H7qTAjHnU@z \
--to=reback00@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).