unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: 39377@debbugs.gnu.org
Subject: bug#39377: guix search reports bad location for bytestructures
Date: Fri, 31 Jan 2020 14:07:42 -0800	[thread overview]
Message-ID: <52d09f27-9b5f-8f8d-1f11-04d1e05e2239@gmail.com> (raw)

I'm using guix-1.0.1 on Fedora 30, x86_64.

I wanted to get module spec for bytestructures, but failed:
location points to (guix packages), but it's actually in (gnu packages 
guile).

$ guix search bytestructures
name: guile3.0-bytestructures
version: 1.0.7
outputs: out
systems: x86_64-linux i686-linux
dependencies: autoconf@2.69 automake@1.16.1 guile-next@3.0.0 
pkg-config@0.29.2
location: guix/packages.scm:880:11
homepage: https://github.com/TaylanUB/scheme-bytestructures
license: GPL 3+
synopsis: Structured access to bytevector contents for Guile
description: Guile bytestructures offers a system imitating the type 
system of
+ the C programming language, to be used on bytevectors.  C's type 
system works
+ on raw memory, and Guile works on bytevectors which are an abstraction 
over
+ raw memory.  It's also more powerful than the C type system, elevating 
types
+ to first-class status.
relevance: 6

$ guix repl
scheme@(guix-user)> guile3.0-bytestructures
;;; <unknown-location>: warning: possibly unbound variable 
`guile3.0-bytestructures'
ERROR: error: guile3.0-bytestructures: unbound variable

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(guix-user) [1]> ,use (gnu packages guile)
scheme@(guix-user) [1]> guile3.0-bytestructures
$1 = #<package guile3.0-bytestructures@1.0.7 guix/packages.scm:880 
7f639f9532c0>

             reply	other threads:[~2020-01-31 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 22:07 Matt Wette [this message]
2020-02-02 22:52 ` bug#39377: guix search reports bad location for bytestructures 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

  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=52d09f27-9b5f-8f8d-1f11-04d1e05e2239@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=39377@debbugs.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).