From: Danny Milosavljevic <dannym@scratchpost.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: GNOME in Guix
Date: Wed, 4 Nov 2020 14:43:50 +0100 [thread overview]
Message-ID: <20201104144350.68cc6d24@scratchpost.org> (raw)
In-Reply-To: <6ea08f910493be04f088db1ac6b98b1ecbd6d968.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
Hi,
On Wed, 04 Nov 2020 10:45:06 +0100
Leo Prikler <leo.prikler@student.tugraz.at> wrote:
> But we already know all this from our earlier discussion.
I *know* you already know that--but "we" don't. I want someone to actually
proceed further, because I cannot. Hence I posted this on guix-devel
(for the first time with an easy short recipe to follow).
> > Now how do I get more info, using Guix tools?
> What kind of information do you even want to gather? To be honest, you
> lose me every time you end up establishing knowledge, that already
> exists between this thread and the mentioned Guile-GI issue.
I am hereby asking someone who knows how this part of guix works to find out
what happens here.
> I suppose if you want to look at how environments are built, building
> them with higher verbosity would be a start, no?
Thanks. That is what I wanted to know.
I tried guix environment -v 99 -d 1 and it adds nothing useful, especially not
how the other libgobject got in there.
So I still want to know.
> For the purpose of this, it would probably suffice to look at something
> simpler than guile-gi in its totality, perhaps just gobject-
> introspection + glib (note, that you'd need Scheme code to access the
> latter).
Sure, sounds good.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-04 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 13:51 GNOME in Guix Leo Prikler
2020-11-03 9:14 ` Danny Milosavljevic
2020-11-03 13:41 ` Leo Prikler
2020-11-03 19:26 ` Danny Milosavljevic
2020-11-03 23:20 ` Leo Prikler
2020-11-04 8:08 ` Danny Milosavljevic
2020-11-04 9:45 ` Leo Prikler
2020-11-04 13:43 ` Danny Milosavljevic [this message]
2020-11-04 14:02 ` Leo Prikler
2020-11-06 9:55 ` Pierre Neidhardt
-- strict thread matches above, loose matches on Subject: below --
2020-10-29 16:25 Guix Front End (GUI) and making it more mainstream, popular in scientific community Aniket Patil
2020-10-29 19:34 ` Danny Milosavljevic
2020-11-02 7:44 ` Pierre Neidhardt
2020-11-02 10:17 ` GNOME in Guix Danny Milosavljevic
2020-11-06 9:41 ` Pierre Neidhardt
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=20201104144350.68cc6d24@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).