From: Marius Bakke <mbakke@fastmail.com>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add inox.
Date: Thu, 12 Jan 2017 19:42:29 +0100 [thread overview]
Message-ID: <8737go6rxm.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAL1_immZ5h1C6EJJWLdmi5Pw5oNcXZjmdgz+dNrYVQz8YSBWVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
David Craven <david@craven.ch> writes:
>>> * no hidpi scaling: didn't there use to be an enable_hdpi flag?
>>> Recompiling with enable_hdpi=true see if that works
>
>> Oops, let us know!
>
> I think that the flag was removed and is the default now. I expect
> that the problem is that some dependencies need to be added to the
> wrapper.
This is likely. The wrapper was added rather hap-hazardly by trying to
start chromium, see which libraries it complained about, and adding
them. There may be some non-fatal libraries missing. I would really
prefer if we could make it link with proper RUNPATHs.
> guix environment --pure --ad-hoc chromium-browser
The package is called "chromium", not "chromium-browser", unless you
renamed it :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-12 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 12:08 [PATCH] gnu: Add inox David Craven
2017-01-10 19:02 ` Leo Famulari
2017-01-10 19:08 ` David Craven
2017-01-10 19:12 ` David Craven
2017-01-10 23:22 ` Marius Bakke
2017-01-11 8:56 ` David Craven
2017-01-11 17:48 ` Marius Bakke
2017-01-11 19:56 ` David Craven
2017-01-11 23:53 ` David Craven
2017-01-12 17:22 ` Marius Bakke
2017-01-12 18:21 ` David Craven
2017-01-12 18:42 ` Marius Bakke [this message]
2017-01-26 19:36 ` David Craven
2017-01-12 9:39 ` ng0
2017-01-10 19:16 ` 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=8737go6rxm.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=david@craven.ch \
--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).