unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Lukas Gradl <lgradl@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add msgpack
Date: Mon, 20 Jun 2016 13:09:49 -0400	[thread overview]
Message-ID: <20160620170949.GA22393@jasmine> (raw)
In-Reply-To: <8737o9onan.fsf@openmailbox.org>

On Sat, Jun 18, 2016 at 10:44:16PM -0500, Lukas Gradl wrote:
> Lukas Gradl <lgradl@openmailbox.org> writes:
> 
> > So the flags -I, -L, -l for zlib are all there for both dynamic and
> > static linking.  But still no store reference.
> 
> I think the reason why there is no reference is that msgpack uses
> zbuffer only for tests.  Before compilation, the file only references
> the name "zlib" and does not mention the hash in the path of zlib in the
> store.  During compilation (during "check"), this mere name "zlib" gets
> somehow resolved to the path of zlib in the store.  The binary file
> resulting from compiling zbuffer should therefore contain a reference to
> zlib, which should be detectable by guix gc --references.  I think
> however, that this binary file does not get installed as it is only used
> for tests.  All the files that do get installed in the output path of
> msgpack in the store do not contain the hash part of the store-path of
> zlib.  They only refer to zlib by name.  IIUC this can not be detected
> by guix gc --references since it only searches for the hash part of
> the store-path of zlib.
> 
> This is what I grasp from looking at libstore/references.cc and
> libstore/store-api.cc.  I am not sure about this though.

That's my understanding as well.

Thanks for trying all the things you described in your previous email.

Since we are still stuck on this, I think we should continue with Ring
and see if this becomes a problem later on. If so, let's contact the
msgpack maintainers and ask for advice.

We should add a caveat in a comment in msgpack's package definition, for
future readers.

I'm curious — how close are you to a Ring package definition?

  reply	other threads:[~2016-06-20 17:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 20:50 [PATCH] Add msgpack Lukas Gradl
2016-05-31 21:45 ` Leo Famulari
2016-06-01  4:49 ` Efraim Flashner
2016-06-03  0:50   ` Lukas Gradl
2016-06-06 14:07 ` Leo Famulari
2016-06-11  3:06   ` Leo Famulari
2016-06-11 23:56     ` Lukas Gradl
2016-06-12  0:17       ` Leo Famulari
2016-06-12  4:24         ` Lukas Gradl
2016-06-13 16:58           ` Leo Famulari
2016-06-13 17:59             ` Leo Famulari
2016-06-17 15:13               ` Lukas Gradl
2016-06-19  3:44                 ` Lukas Gradl
2016-06-20 17:09                   ` Leo Famulari [this message]
2016-06-21 13:55                     ` Lukas Gradl
2016-06-21 16:06                       ` Leo Famulari
2016-06-21 15:59                     ` Lukas Gradl
2016-06-21 16:49                       ` Efraim Flashner
2016-06-22  6:05                         ` Lukas Gradl
2016-06-22  5:56                       ` Lukas Gradl
2016-06-21  8:38                   ` Ludovic Courtès
2016-06-21 13:31                     ` Lukas Gradl
2016-06-21 14:11                       ` Ludovic Courtès
2016-06-25 15:31                 ` Leo Famulari
2016-06-25 16:40                   ` Lukas Gradl

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=20160620170949.GA22393@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=lgradl@openmailbox.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).