all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Thomas Albers Raviola <thomas@thomaslabs.org>
Cc: 50578@debbugs.gnu.org
Subject: [bug#50578] [PATCH] gnu: Add minipro
Date: Sat, 1 Apr 2023 18:46:36 +0100	[thread overview]
Message-ID: <9d150039-5914-37a9-f7c1-2d8554f95099@makinata.eu> (raw)
In-Reply-To: <87lejbmwyk.fsf@alpha.mail-host-address-is-not-set>

On 2023-04-01 16:41, Thomas Albers Raviola via Guix-patches via wrote:
> Hi Bruno,
> 
> yes, I am still maintaining a local copy of this package.
> 
> I have a question regarding your observations though. Could you please
> reference some example in the guix source base, how one is supposed to
> rewrite the fixes as a G-Expression in this context?

I've edited mympd, libavif, autokey, rng-tools, dropwatch and nvme-cli to use
G-Expressions but you can also take a look at other packages for inspiration.

Another source of inspiration is to grep for commits that perform conversion
to G-Expressions.

> I am not familiar with this specific use. Also the manual does not show
> something similar AFAIK.

Right, it's a bit unfortunate in this department at the moment.


Cheers,
Bruno




  reply	other threads:[~2023-04-01 17:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 10:56 [bug#50578] [PATCH] gnu: Add minipro Thomas Albers via Guix-patches via
2023-03-31 11:09 ` Bruno Victal
2023-04-01 15:41   ` Thomas Albers Raviola via Guix-patches via
2023-04-01 17:46     ` Bruno Victal [this message]
2023-04-02 22:13       ` Thomas Albers Raviola via Guix-patches via
2023-04-03 11:17         ` Bruno Victal
2023-04-03 13:20           ` Thomas Albers Raviola via Guix-patches via
2023-04-02 22:08 ` Thomas Albers via Guix-patches via
2023-04-03 13:17 ` Thomas Albers via Guix-patches via
2023-04-22 12:48   ` Bruno Victal
2023-04-23 15:24   ` bug#50578: " Leo Famulari

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=9d150039-5914-37a9-f7c1-2d8554f95099@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=50578@debbugs.gnu.org \
    --cc=thomas@thomaslabs.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.