From: David Pirotte <david@altosw.be>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Wed, 8 May 2024 18:51:11 -0300 [thread overview]
Message-ID: <20240508185111.48b02ad7@tintin> (raw)
In-Reply-To: <87seys37fe.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Hi Florian,
> I tried adw1-demo.scm with the attached patch to replace
> (current-filename), which would return #f so (dirname) throws.
> It fails because it cannot find namespaces. Guix uses libadwaita
> 1.4.0. Is it too old?
Yes, as announced in the NEWS, the release notes, and on the g-golf web
site, you need libadwaita >= 1.5.0
https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/class.Dialog.html
...
since 1.5
David
This reminds me to remind you, for your debian vm installation, you need
to install debian from testing (_not_ stable), which has the g-golf
packages and their required dependencies at the adequate
versions as well - debian offers 4 g-golf packages:
g-golf 0.8.0-rc2-1
g-golf-dbgsym 0.8.0-rc2-1
g-golf-gtk-4-examples 0.8.0-rc2-1
g-golf-adw-1-examples 0.8.0-rc2-1
[ so, nearly the latest, but i've noticed it can take up to a
[ few months so debian releases the upstream releasd version,
[ which can be too much if you are actively working on a
[ project ...
So, with the last commentin mind, you might as well decide to install
from the source [and checkout the devel branch] - let me know if you
need help ... but it is well explained (hopefully well explained) in the
INSTALL file, the manual and on the web site ...
Fwiw, i do _not_ install guile from the debian package either, and
obviously work by constantly compiling/installing from my clone devel
branch as well ...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-08 21:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 5:56 GNU G-Golf 0.8.0-rc-3 available for testing David Pirotte
2024-04-17 22:30 ` pelzflorian (Florian Pelz)
2024-04-18 22:21 ` David Pirotte
2024-04-19 17:00 ` pelzflorian (Florian Pelz)
2024-04-20 4:51 ` David Pirotte
2024-04-20 8:35 ` pelzflorian (Florian Pelz)
2024-04-30 17:51 ` pelzflorian (Florian Pelz)
2024-05-01 0:51 ` David Pirotte
2024-05-01 8:17 ` pelzflorian (Florian Pelz)
2024-05-07 1:39 ` David Pirotte
2024-05-07 9:36 ` pelzflorian (Florian Pelz)
2024-05-07 23:53 ` David Pirotte
2024-05-08 10:49 ` pelzflorian (Florian Pelz)
2024-05-08 21:51 ` David Pirotte [this message]
2024-05-02 18:50 ` pelzflorian (Florian Pelz)
2024-05-02 21:57 ` David Pirotte
2024-05-03 5:00 ` David Pirotte
2024-05-03 11:35 ` pelzflorian (Florian Pelz)
2024-05-04 5:59 ` David Pirotte
2024-05-04 14:31 ` pelzflorian (Florian Pelz)
2024-05-04 18:08 ` pelzflorian (Florian Pelz)
2024-05-04 22:11 ` David Pirotte
2024-05-04 22:23 ` David Pirotte
2024-05-04 21:39 ` David Pirotte
2024-05-05 1:43 ` pelzflorian (Florian Pelz)
2024-05-05 21:30 ` David Pirotte
2024-05-06 9:45 ` pelzflorian (Florian Pelz)
2024-05-06 9:53 ` Basile Starynkevitch
2024-05-06 13:08 ` pelzflorian (Florian Pelz)
2024-05-03 0:17 ` David Pirotte
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240508185111.48b02ad7@tintin \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.
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).