From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Sun, 01 Nov 2020 13:05:54 +0100 [thread overview]
Message-ID: <20201101120554.nD2hRSEQckvQUH-9eSQkchApEXH9t7pzECaptZ0YGRI@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: 1382 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/25901#issuecomment-720078121
Comment:
https://github.com/void-linux/void-packages/compare/master...ymir-linux:master if you don't want to diff with git diff.
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.
My position is, 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.
There are a few possibilities how this would end up:
* We ignore those patches and libre build options and they are going to break from time to time:
* Users who build those packages with libre options will complain, open Issues and PRs = more work.
* We have to additionally test and update libre patches we don't care at all about = a lot more work.
With the current situation, the people who care about libre stuff can just use git to merge our repository with their changes, git is pretty smart about merging changes as it is its main purpose, maintaining a set of patches by hand seems backwards.
There is no extra work for us and the work for the libre maintainers its a very similiar amount of work as they only have to additionally resolve merge conflicts.
next prev parent reply other threads:[~2020-11-01 12:05 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 [this message]
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 ` [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=20201101120554.nD2hRSEQckvQUH-9eSQkchApEXH9t7pzECaptZ0YGRI@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).