From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@member.fsf.org>
Cc: 31462@debbugs.gnu.org
Subject: [bug#31462] [PATCH] profiles: Add hook to generate "gschemas.compiled".
Date: Thu, 17 May 2018 17:56:50 +0200 [thread overview]
Message-ID: <87k1s2xol9.fsf@gnu.org> (raw)
In-Reply-To: <874lj6pkdf.fsf@member.fsf.org> ("宋文武"'s message of "Thu, 17 May 2018 19:55:08 +0800")
Hey,
iyzsong@member.fsf.org (宋文武) skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello!
>>
>> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>>
>>> * guix/profiles.scm (glib-schemas): New procedure.
>>> (%default-profile-hooks): Add it.
>>
>> [...]
>>
>>> + (mlet %store-monad ((%glib (manifest-lookup-package manifest "glib"))
>>> + ;; XXX: Can't use glib-compile-schemas corresponding
>>> + ;; to the glib referenced by 'manifest'. Because
>>> + ;; '%glib' can be either a package or store path, and
>>> + ;; there's no way to get the "bin" output for the later.
>>> + (glib-compile-schemas
>>> + -> #~(string-append #+glib:bin
>>> + "/bin/glib-compile-schemas")))
>>
>> Oh right, too bad.
>>
>> 宋文武, any comments, since you wrote the existing hooks in that area?
>>
>
> Well, I think this situation is not changed. Our profile hooks
> currently use latest version of zlib, gzip, guile-gdbm-ffi, gtk+, ghc
> and etc. We'd like to use packages from the manifest to avoid
> additional downloads, but it's not awlays possible...
Right, so that’s not new.
You’re OK with the rest of the patch?
Thanks for your quick reply!
Ludo’.
next prev parent reply other threads:[~2018-05-17 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 12:49 [bug#31462] [PATCH] profiles: Add hook to generate "gschemas.compiled" Danny Milosavljevic
2018-05-17 8:57 ` Ludovic Courtès
2018-05-17 11:55 ` 宋文武
2018-05-17 15:56 ` Ludovic Courtès [this message]
2018-05-19 4:34 ` 宋文武
2018-05-20 20:32 ` Ludovic Courtès
2018-05-25 9:16 ` bug#30642: " Ludovic Courtès
2018-05-25 9:16 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1s2xol9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31462@debbugs.gnu.org \
--cc=iyzsong@member.fsf.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.