unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brendan Tildesley <mail@brendan.scot>
To: Prafulla Giri <pratheblackdiamond@gmail.com>
Cc: 43151@debbugs.gnu.org
Subject: bug#43151: Resolve Calibre run-time dependency
Date: Mon, 7 Sep 2020 18:15:15 +1000	[thread overview]
Message-ID: <6492c3cc-07e0-b56b-ea72-99d403770755@brendan.scot> (raw)
In-Reply-To: <a99e52ae-decc-0396-6d4e-d3dff56dd5d2@brendan.scot>

Sorry I tried sending this with a typo in your gmail address so I'm 
resending just for you:

On 7/9/20 6:12 pm, Brendan Tildesley wrote:
> There is actually a Bug report by Andreas for this very issue. I 
> created a bug report just for updating, and fixed this issue after it 
> while I could, without realising. Sorry for all the confusion with 
> things happening in 3 different threads.
>
> I created an updated patch just for this one here. 
> https://issues.guix.gnu.org/43151#5
>
> Your patch also works I think but it will wrap the programs twice, so 
> you will get calibre, .calibre-real, and ..calibre-real-real, etc for 
> every program, which seems ugly. My patch reproduces the same 
> PYTHONPATH that is set in python-build-system in addition to wrapping 
> PYTHONPATH (unless I made a mistake), although at the cost of code 
> duplication. I leave it to you and who ever is reviewing this to 
> decide which way is more correct and push one, haha.
>
>
> Please continue any discussion of the QtWebEngine bug on issue 43121: 
> 43151@debbugs.gnu.org / https://issues.guix.gnu.org/43151






       reply	other threads:[~2020-09-07  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a99e52ae-decc-0396-6d4e-d3dff56dd5d2@brendan.scot>
2020-09-07  8:15 ` Brendan Tildesley [this message]
2020-09-08 20:11   ` bug#43151: Resolve Calibre run-time dependency Andreas Enge

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=6492c3cc-07e0-b56b-ea72-99d403770755@brendan.scot \
    --to=mail@brendan.scot \
    --cc=43151@debbugs.gnu.org \
    --cc=pratheblackdiamond@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).