unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: libjpeg-8 not installable
Date: Sun, 20 Jan 2013 12:58:01 +0100	[thread overview]
Message-ID: <201301201258.01463.andreas@enge.fr> (raw)
In-Reply-To: <87y5foyi6u.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Am Samstag, 19. Januar 2013 schrieb Ludovic Courtès:
> This has to do with how guix-package interprets package names.
> 
> As noted in the manual, users can write either “guix-package -i guile”
> or “guix-package -i guile-2.0.7”.  In the latter case, guix-package
> assumes that “2.0.7” is a version number, and then searches all packages
> whose name is “guile” and whose version is “2.0.7”.
> 
> In your case, it searches for packages named “libjpeg” and whose version
> number is “8”–which fails.
> 
> The fix it to not introduce the version number in the ‘name’ field, and
> instead leave it in the ‘version’ field.

Thanks for the explanation. I was confusing scheme variable names and 
package names, which are the same most of the time. With
(define-public libjpeg-8
  (package (inherit libjpeg)
   (name "libjpeg")
   (version "8d")

$ guix-package -i libjpeg-8d
indeed works as expected.

However, now
$ guix-build libjpeg-8d
returns
libjpeg-8d: unknown package
Using the scheme variable name does not help:
$ guix-build libjpeg-8
libjpeg-8: unknown package

Could the behaviour of guix-build be made the same as that of guix-package?

Andreas

[-- Attachment #2: Type: text/html, Size: 6633 bytes --]

  reply	other threads:[~2013-01-20 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 11:16 libjpeg-8 not installable Andreas Enge
2013-01-19 21:30 ` Ludovic Courtès
2013-01-20 11:58   ` Andreas Enge [this message]
2013-01-22 21:40     ` Ludovic Courtès
2013-01-23 20:28       ` Andreas Enge
2013-01-23 23:13         ` 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=201301201258.01463.andreas@enge.fr \
    --to=andreas@enge.fr \
    --cc=bug-guix@gnu.org \
    --cc=ludo@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).