unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Jessica Tallon <tsyesika@tsyesika.se>
Cc: 61117@debbugs.gnu.org
Subject: [bug#61117] Update svtplay-dl to 4.18
Date: Sat, 28 Jan 2023 13:33:44 +0100	[thread overview]
Message-ID: <87357ult1k.fsf@nckx> (raw)
In-Reply-To: <5646122.DvuYhMxLoT@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

Jessica,

Jessica Tallon 写道:
> I've attached a patch to upgrade svtplay-dl from 4.17 to 4.18.

Thanks!

> I've also moved ffmpeg form inputs to propagated-inputs

Please avoid propagation whenever possible; it breaks all kinds of 
nice things.

Propagating A from B means that Guix will effectively ‘install’ A 
alongside B when the user installs only B.  Or how classical 
package managers bluntly handle ‘dependencies’.  Not good!

Here's what I'd do instead [untested]:

    (arguments
     (list #:phases
           #~(modify-phases %standard-phases
               (add-after 'wrap 'wrap-harder
                 (lambda* (#:key inputs outputs 
                 #:allow-other-keys)
                   (wrap-script (string-append (assoc-ref outputs 
                   "out")
                                               "/bin/svtplay-dl")
                     `("PATH" ":" prefix
                       (,(dirname (search-input-file inputs
                                                     "bin/ffmpeg"))))))))))
    (native-inputs (list guile-3.0))    ; for wrap-script

> it's needed while the program is 
> running to merge two files, not while building.

So 4.17 did not need or use ffmpeg this way?

Otherwise, put each unrelated changes into a separate commit: one 
to improve the ffmpeg situation, and one to update svtplay-dl. 
You can send multiple related commits as one patch series to one 
bug number, though.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2023-01-28 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 11:29 [bug#61117] Update svtplay-dl to 4.18 Jessica Tallon
2023-01-28 12:33 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2023-01-28 12:58   ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-28 13:02   ` Tobias Geerinckx-Rice via Guix-patches via
2023-03-05 10:05   ` Jessica Tallon
2023-03-05 10:39   ` Jessica Tallon
2023-03-05 20:13   ` Leo Famulari
2023-03-05 20:15     ` Jessica Tallon
2023-03-05 20:58       ` Leo Famulari

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=87357ult1k.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=61117@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=tsyesika@tsyesika.se \
    /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).