unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Christopher Baines <mail@cbaines.net>, thierry@moncourriel.eu
Cc: 38840-done@debbugs.gnu.org
Subject: bug#38840: [PATCH] update python-py3status 3.21 to python-xyz.scm
Date: Fri, 20 Nov 2020 22:17:36 +0100	[thread overview]
Message-ID: <87eeknramn.fsf@gnu.org> (raw)
In-Reply-To: <87sg93kchl.fsf@cbaines.net>

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

Christopher Baines <mail@cbaines.net> skriver:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> thierry@moncourriel.eu writes:
>>
>>> From c759d206188cbabb17198614247dbbeb9d4803bf Mon Sep 17 00:00:00 2001
>>> From: Grillon <thierry@moncourriel.eu>
>>> Date: Tue, 31 Dec 2019 23:25:55 +0100
>>> Subject: [PATCH] gnu: python-py3status: Update file dependency
>>>
>>> * gnu/packages/python-xyz.scm (python-py3status): Update file as
>>> propagated dependecy
>>
>> Thanks!  Do you know how "file" is used for py3status?  Ideally we would
>> patch all invokations of "file" so that it uses the absolute file name,
>> instead of propagating it, along these lines:
>>
>>   (substitute* "foo.py"
>>     (("'file'") (string-append "'" (which "file") "'")))
>>
>> Can you see if such an approach is feasible for python-py3status?
>
> It's been a few months, is this patch still relevant?

It looks like this was fixed by Jakub in
6a6b8a3fcfc35a5e7b10e7c2a9a75e909354d4d6.  Closing, thanks for the
reminder!

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

      reply	other threads:[~2020-11-20 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 22:42 [bug#38840] [PATCH] update python-py3status 3.21 to python-xyz.scm thierry
2020-01-12 21:13 ` Marius Bakke
2020-11-20 20:19   ` Christopher Baines
2020-11-20 21:17     ` Marius Bakke [this message]

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=87eeknramn.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=38840-done@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=thierry@moncourriel.eu \
    /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).