unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: GNOME in Guix
Date: Wed, 04 Nov 2020 15:02:12 +0100	[thread overview]
Message-ID: <3717888bbc4ea8b129880a89dfa916e1e134b84f.camel@student.tugraz.at> (raw)
In-Reply-To: <20201104144350.68cc6d24@scratchpost.org>

Hi,

Am Mittwoch, den 04.11.2020, 14:43 +0100 schrieb Danny Milosavljevic:
> 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).
Ah, okay.  I'm still a bit confused, given how verbose that recipe was,
but I get where you're coming from.

> 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.
I think some important information gets lost here, because you already
built most of the packages.  You could try garbage-collecting them and
then start anew, but then you'd be building the entire profile at full
debug info.  Interestingly, nothing shows up for the generation of
profile.drv, which might indicate, that there are not actually two
packages in there.  It's at least a bit suspicious.

Having received the path of the profile.drv, you might now want to look
at what packages it references (recursively), specifically all mentions
of glib.  (Use emacs-guix for quick navigation through .drv files.)

For the record, in case you forgot to note the .drv, my profile
containing glib-with-documentation and gobject-introspection is

/gnu/store/cl1wz5wsgjy208n330z4p9f5kljzixp2-profile.drv

Regards, Leo



  reply	other threads:[~2020-11-04 14:02 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
2020-11-04 14:02               ` Leo Prikler [this message]
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=3717888bbc4ea8b129880a89dfa916e1e134b84f.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=dannym@scratchpost.org \
    --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).