all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: 69550@debbugs.gnu.org
Subject: bug#69550: smithforth: missing source (?)
Date: Tue, 10 Sep 2024 15:52:45 +0200	[thread overview]
Message-ID: <87ldzzehua.fsf@gmail.com> (raw)
In-Reply-To: <ZeYb_RbFdql2JDWy@theoden> (Christopher Howard's message of "Mon,  4 Mar 2024 10:07:41 -0900")

Hi,

On Mon, 04 Mar 2024 at 10:07, Christopher Howard <christopher@librehacker.com> wrote:

> ``` guix build -S smithforth
> /gnu/store/4w4v7zv4vif2k55g9srmv57fg5icpl94-SForth220711dmp.txt
> ```
>
> ...I only get the annotated header/opcode file. However, the forth system provided in the binary includes also the words defined here:
>
> {https://dacvs.neocities.org/SF/system220711fs.txt}
>
> It seems to me that `guix build -S' should return both these files in some form. Maybe in a tar file...?

No, “guix build -S” returns the ’source’ of the package, i.e., only one
’origin’.  Here it reads:

    (source
      (origin
        (method url-fetch)
        (uri (string-append "https://dacvs.neocities.org/SF/SForth"
                            version "dmp.txt"))
        (sha256
          (base32 "0a39pv7529llsa3f48fmvwvlcp3f9v8qkn5ziw2l6kxf0qvli3lm"))))

The other is listed as inputs:

    (native-inputs (list xxd
                         (origin
                           (method url-fetch)
                           (uri (string-append
                                 "https://dacvs.neocities.org/SF/system"
                                 version "fs.txt"))
                           (sha256
                            (base32
                             "17v1pp64s6n8q8w3kg48nd7zdcx2208y4svr5fpfms5lkyzg7z1m")))))

Therefore, you can run:

--8<---------------cut here---------------start------------->8---
$ guix build smithforth --sources=all
/gnu/store/4w4v7zv4vif2k55g9srmv57fg5icpl94-SForth220711dmp.txt
/gnu/store/lvrkhx3yzjk58ma99vyp0blvr2whbvpr-system220711fs.txt
--8<---------------cut here---------------end--------------->8---

However, this does not work as-is yet; you need
<https://issues.guix.gnu.org/73073>.

Well, I think that’s not a bug.  WDYT?  Closing?

Cheers,
simon




  reply	other threads:[~2024-09-10 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 19:07 bug#69550: smithforth: missing source (?) Christopher Howard
2024-09-10 13:52 ` Simon Tournier [this message]
2024-09-10 17:37   ` Christopher Howard
2024-09-20 16:26     ` Simon Tournier

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=87ldzzehua.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=69550@debbugs.gnu.org \
    --cc=christopher@librehacker.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.