all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Antonio Carlos Padoan Junior" <acpadoanjr@yahoo.com.br>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix package path
Date: Fri, 30 Dec 2022 15:57:43 +0100	[thread overview]
Message-ID: <87y1qpj5w8.fsf@gmail.com> (raw)
In-Reply-To: <87len02xbc.fsf@gnu.org>

Hi Ludo,

On Wed, 21 Dec 2022 at 23:42, Ludovic Courtès <ludo@gnu.org> wrote:

> We don’t have enough info to be sure, but could it be that there are two
> ‘gtklp’ packages in your package collection, for instance because
> ‘gtklp-bad-tool’ is also public?  ‘specification->package’ prints a
> warning if it’s ambiguous.

I do not think the issue is about your assumption.  I guess it is about
Guile modules and compilation.

The package gtklp-bad-tool is defined by:

--8<---------------cut here---------------start------------->8---
(define-public gtklp-bad-tool
  (package
    (name "gtklp")
    (version "1.3.4")
[...]
--8<---------------cut here---------------end--------------->8---

Then gtklp is defined by:

--8<---------------cut here---------------start------------->8---
(define-public gtklp
  (let ((toolchain (specification->package "clang-toolchain@10")))
    (package-with-c-toolchain gtklp-bad-tool `(("toolchain" ,toolchain)))))
--8<---------------cut here---------------end--------------->8---

Here, the issue is ’(specification->package "clang-toolchain@10")’.  For
instance, you get:

    $ guix show -L /tmp/my-guix sbcl-lispiec
    guix show: error: sbcl-lispiec: package not found

where nothing is ambiguous; the package ’sbcl-lispiec’ is unrelated to
both gtklp-bad-tool or gtklp.

If you replace [1] ’specification->package’ by the symbol
clang-toolchain-10, then it just works.

Last, if you use the broken channel with ’specification->package’ but
instead of --load-path, you run “time-machine” or “pull”, then the issue
is gone.


https://gitlab.com/acpadoanjr/my-guix/-/blob/0e540b6fce0409330cb1ca3453d81f18c8e60163/my-packages/extra.scm#L71-115
https://gitlab.com/acpadoanjr/my-guix/-/blob/0e540b6fce0409330cb1ca3453d81f18c8e60163/my-packages/extra.scm#L313-315
1: <https://yhetil.org/guix/87cz8fo412.fsf@gmail.com>


Cheers,
simon


      reply	other threads:[~2022-12-30 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wn6nzx2g.fsf.ref@yahoo.com.br>
2022-12-19  7:12 ` guix package path Antonio Carlos Padoan Junior
2022-12-19 10:47   ` zimoun
2022-12-19 12:06     ` Antonio Carlos Padoan Junior
2022-12-19 14:35       ` zimoun
2022-12-20 21:38       ` Antonio Carlos Padoan Junior
2022-12-21 22:42         ` Ludovic Courtès
2022-12-30 14:57           ` zimoun [this message]

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=87y1qpj5w8.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=acpadoanjr@yahoo.com.br \
    --cc=guix-devel@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 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.