From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: r: Add pango to inputs.
Date: Fri, 17 Jun 2016 14:26:17 +0200 [thread overview]
Message-ID: <idjh9csvw5y.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20160617101312.11798-1-ricardo.wurmus@mdc-berlin.de>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Hi Guix,
>
> our R package is currently built with Cairo, which allows R to use the Cairo
> rendering backend. When R starts up and loads grDevices, however, it checks
> for the availability of Pango, not Cairo. So even though the Cairo backend
> works just fine, R falls back to using the primitive Xlib backend.
>
> You can confirm this by running this in R:
>
> getOption('bitmapType')
> options(bitmapType='cairo')
>
> The first command should show you "Xlib" with R from Guix. The second sets
> the backend to Cairo, which works without problems.
>
> I decided against patching the detection mechanism in R because I don't know
> if R might use Pango features elsewhere. Instead I opted to add Pango to the
> inputs. Pango pulls in Cairo, so the package closure is a little bigger than
> before. Pango makes up 0.7% of the total size, so I think that's okay.
>
> ~~ Ricardo
I also just stumbled upon an old message to the mailing list, which I
had completely forgotten about:
http://lists.gnu.org/archive/html/guix-devel/2015-09/msg00279.html
This is the very same problem and it is solved by giving R what it
wants: Pango.
~~ Ricardo
prev parent reply other threads:[~2016-06-17 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 10:13 [PATCH] gnu: r: Add pango to inputs Ricardo Wurmus
2016-06-17 10:13 ` Ricardo Wurmus
2016-06-17 15:18 ` Ludovic Courtès
2016-06-28 7:36 ` Ricardo Wurmus
2016-06-17 12:26 ` Ricardo Wurmus [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=idjh9csvw5y.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.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.
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).