From: Leo Famulari <leo@famulari.name>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 25356@debbugs.gnu.org, dian_cecht@zoho.com
Subject: bug#25356: livestreamer no longer supported
Date: Tue, 30 Jan 2018 00:01:26 -0500 [thread overview]
Message-ID: <20180130050126.GA10166@jasmine.lan> (raw)
In-Reply-To: <87k1w6g89l.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Thu, Jan 25, 2018 at 02:13:42AM +0300, Oleg Pykhalov wrote:
> Leo Famulari <leo@famulari.name> writes:
> > Ideally both packages' executables would have the same name.
>
> Symlink? :-)
If streamlink doesn't already provide a 'livestreamer' executable for
compatibility, I'd rather not add one.
It's a matter of taste, but I think we should avoid changing upstream
software for non-technical reasons or without overwhelming user demand
:)
This is in contrast to some distros like Debian which patch their
packages very heavily, basically creating new forks in some cases.
Note that we already had a rather high-profile deprecation with
executable name-change when certbot was renamed from letsencrypt by the
upstream developers. Any users had to adapt their scripts to account for
the new name.
So, my weak preference is to supersede livestreamer with streamlink
without creating the symlink.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-30 5:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:05 bug#25356: livestreamer no longer supported dian_cecht
2018-01-24 22:17 ` Oleg Pykhalov
2018-01-24 22:27 ` Leo Famulari
2018-01-24 23:13 ` Oleg Pykhalov
2018-01-30 5:01 ` Leo Famulari [this message]
2018-01-30 7:10 ` Oleg Pykhalov
2018-01-30 22:46 ` Leo Famulari
2018-01-31 3:41 ` Oleg Pykhalov
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180130050126.GA10166@jasmine.lan \
--to=leo@famulari.name \
--cc=25356@debbugs.gnu.org \
--cc=dian_cecht@zoho.com \
--cc=go.wigust@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).