all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: cage <cage-dev@twistfold.it>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 65097@debbugs.gnu.org, cage <cage-dev@twistfold.it>
Subject: [bug#65097] [PATCH] gnu: Add tk-img.
Date: Wed, 6 Sep 2023 19:42:33 +0200	[thread overview]
Message-ID: <ZPi6CUwSeQv8LPa2@shimizu.casa.net> (raw)
In-Reply-To: <87il8n5lrd.fsf@gmail.com>

On Wed, Sep 06, 2023 at 12:06:46PM -0400, You wrote:
> Hi!

Hi!

[...]

> > Because I was not able to find out the contribs sources.
>
> (assuming the source is a gzipped tarball)
>
> If you './pre-inst-env guix build --source tk-img', then unpack it to
> /tmp with 'tar xf /gnu/store...-cage.tar.gz -C /tmp', you should then be
> able to look at what it contains, e.g.
>
> find /tmp/cage-x.y.z/ -name '*contrib*'

So they were hiding under the "compat" directory! :D

I have learnt a new (to me) guix switch ("--source"), thanks!

> > Also, for the record, the problem with  tests is not that the Tk (as I
> > erroneously thought)  executable can not  be found but that,  for some
> > reasons, the tcl script seems to fails to resolve Tk as dependency:
> >
> > $ tclsh
> >
> > % package require Tk → raise an error
>
> Oh!  So it seems we have a bigger problem to resolve first :-)
>
> Thanks for your investigations.

My pleasure, I am happy if I  can give a contribution to guix, even if can be only
minimal.

Bye!
C.




  reply	other threads:[~2023-09-06 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05 13:45 [bug#65097] [PATCH] gnu: Add tk-img cage
2023-09-05 14:21 ` Maxim Cournoyer
2023-09-05 14:43   ` Maxim Cournoyer
2023-09-05 17:11   ` cage
2023-09-05 14:22 ` Maxim Cournoyer
2023-09-06 14:06 ` cage
2023-09-06 16:06   ` Maxim Cournoyer
2023-09-06 17:42     ` cage [this message]
2023-11-16 15:39 ` [bug#65097] failed attempt cage

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=ZPi6CUwSeQv8LPa2@shimizu.casa.net \
    --to=cage-dev@twistfold.it \
    --cc=65097@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.