From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re:  gstreamer1: update to 1.18.1
Date: Sun, 20 Dec 2020 19:11:49 +0100 [thread overview]
Message-ID: <20201220181149.PEvZVE_0rEdA0KYxAbk34dENguVHVfnYxikN5HV0x48@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26411@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/26411#issuecomment-748641264
Comment:
what has been asked for or added does not matter - we're not the upstream, so we have no responsibility for maintaining entire components added on top, and as you can see, if we do that it leads to unfortunate incidents with upstream projects; i *really* don't want to become another gentoo, where our users come to upstreams with bug reports caused by their outlandish setups
if people want those features available, they should go to upstream, open reports and PRs there, and *then* we can pull it downstream, but maintaining entire new features within a distro is really bad
if we have other packages where features are patched in like this too, these are also candidates for removal
next prev parent reply other threads:[~2020-12-20 18:11 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 20:28 [PR PATCH] " ndowens
2020-11-15 20:53 ` [PR PATCH] [Updated] " ndowens
2020-11-15 20:53 ` ndowens
2020-11-15 21:20 ` ndowens
2020-11-15 22:40 ` [PR REVIEW] " fosslinux
2020-11-15 22:47 ` ericonr
2020-11-15 22:47 ` ericonr
2020-11-15 22:47 ` ericonr
2020-11-15 22:57 ` ndowens
2020-11-15 22:57 ` q66
2020-11-15 22:58 ` ericonr
2020-11-15 23:00 ` q66
2020-11-15 23:55 ` ndowens
2020-11-15 23:57 ` [PR PATCH] [Updated] " ndowens
2020-11-16 0:04 ` [PR REVIEW] " ndowens
2020-11-16 0:54 ` q66
2020-11-16 0:58 ` ndowens
2020-11-16 0:59 ` [PR PATCH] [Updated] " ndowens
2020-11-16 1:18 ` [PR REVIEW] " ericonr
2020-11-16 1:24 ` q66
2020-11-16 13:30 ` ericonr
2020-11-16 15:22 ` [PR PATCH] [Updated] " ndowens
2020-12-17 9:00 ` lane-brain
2020-12-17 9:00 ` lane-brain
2020-12-17 20:23 ` ndowens
2020-12-17 20:28 ` fosslinux
2020-12-19 18:15 ` the-eater
2020-12-19 20:17 ` ndowens
2020-12-19 23:28 ` fosslinux
2020-12-19 23:42 ` ericonr
2020-12-20 16:12 ` the-eater
2020-12-20 17:03 ` q66
2020-12-20 17:46 ` [PR PATCH] [Updated] " ndowens
2020-12-20 17:46 ` ndowens
2020-12-20 17:48 ` [PR PATCH] [Updated] " ndowens
2020-12-20 17:49 ` ndowens
2020-12-20 17:56 ` ndowens
2020-12-20 18:03 ` ericonr
2020-12-20 18:10 ` q66
2020-12-20 18:11 ` q66 [this message]
2020-12-21 1:31 `  gstreamer1: update to 1.18.2 fosslinux
2020-12-21 1:40 ` q66
2020-12-21 2:09 ` ericonr
2020-12-21 2:14 ` ericonr
2020-12-21 2:15 ` ericonr
2020-12-21 2:19 ` ericonr
2020-12-21 2:47 ` travankor
2020-12-21 2:47 ` travankor
2020-12-21 2:47 ` q66
2020-12-21 2:47 ` travankor
2020-12-21 2:48 ` q66
2020-12-21 2:52 ` q66
2020-12-21 2:55 ` ericonr
2020-12-21 2:57 ` ericonr
2020-12-21 2:57 ` q66
2020-12-21 2:58 ` q66
2020-12-21 2:58 ` q66
2020-12-21 2:59 ` q66
2020-12-21 3:03 ` ericonr
2020-12-21 3:13 ` q66
2020-12-21 15:40 ` ndowens
2020-12-21 15:41 ` ndowens
2020-12-21 20:36 ` ericonr
2020-12-21 21:06 ` [PR PATCH] [Updated] " ndowens
2020-12-21 21:28 ` [PR REVIEW] " ericonr
2020-12-21 21:31 ` ndowens
2020-12-22 0:12 ` [PR PATCH] [Updated] " ndowens
2020-12-22 0:14 ` ndowens
2020-12-22 0:22 ` ndowens
2020-12-22 0:30 ` ndowens
2020-12-22 1:03 ` ndowens
2020-12-22 1:46 ` ndowens
2020-12-22 2:43 ` ndowens
2020-12-30 9:57 ` [PR REVIEW] " travankor
2020-12-30 12:05 ` [PR PATCH] [Updated] " ndowens
2020-12-30 12:07 ` [PR REVIEW] " ndowens
2021-01-10 7:46 ` travankor
2021-01-17 2:38 ` travankor
2021-01-17 3:08 ` ndowens
2021-01-17 3:08 ` [PR PATCH] [Closed]: " ndowens
2021-01-17 23:01 ` travankor
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=20201220181149.PEvZVE_0rEdA0KYxAbk34dENguVHVfnYxikN5HV0x48@z \
--to=q66@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).