From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: 62629@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>
Subject: [bug#62629] [PATCH] gnu: guile-pipe: Remove unused install script.
Date: Fri, 12 May 2023 20:52:02 +0200 [thread overview]
Message-ID: <873541bcx9.fsf@jpoiret.xyz> (raw)
In-Reply-To: <20230402200322.20226-1-jgart@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Hi jgart,
jgart via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/guile-xyz.scm (guile-pipe): Remove script.
> ---
> gnu/packages/guile-xyz.scm | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm
> index fd8fb25da1..691635e155 100644
> --- a/gnu/packages/guile-xyz.scm
> +++ b/gnu/packages/guile-xyz.scm
> @@ -362,7 +362,10 @@ (define-public guile-pipe
> (commit commit)))
> (file-name (git-file-name name version))
> (sha256
> - (base32 "038gwrhfywgs8372q478wn4623lhcmkknfj4p8yaa93bykfc0fml"))))
> + (base32 "038gwrhfywgs8372q478wn4623lhcmkknfj4p8yaa93bykfc0fml"))
> + (modules '((guix build utils)))
> + ;; Remove unused install script.
> + (snippet '(begin (delete-file "install")))))
> (build-system guile-build-system)
> (native-inputs
> (list guile-3.0))
> --
> 2.39.2
Is this really necessary? guile-pipe builds fine without it and this
doesn't end up in the output, right?
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-05-12 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 20:03 [bug#62629] [PATCH] gnu: guile-pipe: Remove unused install script jgart via Guix-patches via
2023-05-12 18:52 ` Josselin Poiret via Guix-patches via [this message]
2023-05-12 21:18 ` jgart via Guix-patches via
2023-05-13 7:39 ` bug#62629: " Josselin Poiret via Guix-patches via
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=873541bcx9.fsf@jpoiret.xyz \
--to=guix-patches@gnu.org \
--cc=62629@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jgart@dismail.de \
/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.