all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Reusing code for a build-phase?
Date: Sun, 6 Aug 2023 16:23:56 +0100	[thread overview]
Message-ID: <4129ecad-2300-fd32-55e9-9f93a2a4d5ac@makinata.eu> (raw)
In-Reply-To: <68aacdad-ecd3-2e82-db4b-c9c85bb8e520@crazy-compilers.com>

Hi Hartmut,

On 2023-08-05 09:25, Hartmut Goebel wrote:
> Hi,
> 
> I'm currently packaging vagrant and some plugins. For all plugins an additional phase is required, generating a json file, see below. Since this is quite some code, I'd like to put it into some definition or some wrapper. Since it uses (this-package-verion), my attempts failed.
> 
> At best, a plugin would then be defined like
> 
>   (define-public vagrant-abc (vagrant-plugin-wrapper (package …
> 
> Anyhow I'd be happy to when being able to use some function in the phase instead of duplicating the code.
> 
> Any ideas? Many thanks in advance

I think using a procedure like you're suggesting here would be alright for this.
Perhaps <https://issues.guix.gnu.org/63081#8> could serve as inspiration?


-- 
Furthermore, I consider that nonfree software must be eradicated.

Cheers,
Bruno.



      parent reply	other threads:[~2023-08-06 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  8:25 Reusing code for a build-phase? Hartmut Goebel
2023-08-06 12:49 ` Csepp
2023-08-06 13:23   ` Hartmut Goebel
2023-08-08  0:15     ` Csepp
2023-08-06 15:23 ` Bruno Victal [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=4129ecad-2300-fd32-55e9-9f93a2a4d5ac@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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.