unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Parnikkapore via Guix-patches via <guix-patches@gnu.org>
To: 61365@debbugs.gnu.org
Subject: [bug#61365] [PATCH] gnu: dino: Update to 0.4.0.
Date: Wed, 08 Feb 2023 20:50:11 +0800	[thread overview]
Message-ID: <9ccff7cc635e12cb8fe33280044bc2163103b6c1.camel@yahoo.com> (raw)
In-Reply-To: <e2460612815844630778d6362207b3972cd05c05.1675847846.git.poomklao@yahoo.com>

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

Hi all,

The closure size of Dino for me is 2034.4 MiB for 0.4 (running under pre-inst-env) and 1420.3 MiB for 0.3.

While investigating this, I found that the size of gtk's transitive closure has also almost doubled; 1961.3 MiB for gtk (i.e. gtk4) and 1002.2 MiB for gtk+ (i.e. gtk3). Interestingly, gtk contains *both* gtk+-3.24.30 and gtk+-2.24.33 in its transitive closure. Something is definitely not right...

> I tried running dino 0.4.0 on my Librem 5 (via guix copy).  
> It crashes directly:  
> libGLESv2.so.2: cannot open shared object file: No such file or directory

That sounds more like a missed input somewhere down the chain to me. Does any other libadwaita / gtk4 app work on the Librem?

[-- Attachment #2: Type: text/html, Size: 795 bytes --]

  parent reply	other threads:[~2023-02-08 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e2460612815844630778d6362207b3972cd05c05.1675847846.git.poomklao.ref@yahoo.com>
2023-02-08  9:17 ` [bug#61365] [PATCH] gnu: dino: Update to 0.4.0 Parnikkapore via Guix-patches via
2023-02-08 10:31   ` Ricardo Wurmus
2023-02-08 12:38   ` Jonathan Brielmaier
2023-02-08 12:50   ` Parnikkapore via Guix-patches via [this message]
2023-02-08 17:02   ` Jonathan Brielmaier
2023-02-12  3:18   ` Morgan Smith
2023-02-19  7:38   ` bug#61365: " Liliana Marie Prikler

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=9ccff7cc635e12cb8fe33280044bc2163103b6c1.camel@yahoo.com \
    --to=guix-patches@gnu.org \
    --cc=61365@debbugs.gnu.org \
    --cc=poomklao@yahoo.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).