all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: Omar Bassam <omar.bassam88@gmail.com>
Cc: jgart <jgart@dismail.de>, Suhail Singh <suhailsingh247@gmail.com>,
	75394-done@debbugs.gnu.org
Subject: [bug#75394] [PATCH v14 0/2] Add jpm.
Date: Wed, 08 Jan 2025 10:30:42 -0500	[thread overview]
Message-ID: <87jzb5tja5.fsf@gmail.com> (raw)
In-Reply-To: <877c77ccwy.fsf@gmail.com> (Omar Bassam's message of "Tue, 07 Jan 2025 09:15:41 +0200")

Omar Bassam <omar.bassam88@gmail.com> writes:

> Yes, Thanks Suhail, your reviews helped me alot.

You're welcome :)

> I would like to contribute more to guix and would like to take building
> a janet-build-system as a start. I would appreciate any guidance or
> recommendations on where to start to learn about building a custom build
> system.

I don't have any specific guidance other than to look at existing build
system definitions.  Perhaps jgart has some thoughts?

>>> In that case, then you can document any special instructions for using
>>> Guix with janet.
>>
>> I do agree that that would be helpful.
>>
>
> I am not sure where should such document be added?

I am no authority, but perhaps the Cookbook?  Jgart, thoughts?

-- 
Suhail




  reply	other threads:[~2025-01-08 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06  1:22 [bug#75394] [PATCH v14 0/2] Add jpm Suhail Singh
2024-10-08  3:22 ` [bug#75394] [PATCH v14 2/2] gnu: Improve user-experience for jpm Suhail Singh
2025-01-06  2:14   ` bug#75394: [PATCH v14 0/2] Add jpm jgart via Guix-patches via
2025-01-07  1:56     ` [bug#75394] " Suhail Singh
2025-01-07  2:51       ` jgart via Guix-patches via
2025-01-07  3:09         ` Suhail Singh
2025-01-07  7:15           ` Omar Bassam
2025-01-08 15:30             ` Suhail Singh [this message]
2024-10-08  3:31 ` [bug#75394] [PATCH v14 1/2] gnu: Add jpm package Suhail Singh

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=87jzb5tja5.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=75394-done@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=omar.bassam88@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.