From: Omar Bassam <omar.bassam88@gmail.com>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: jgart <jgart@dismail.de>, 75394-done@debbugs.gnu.org
Subject: [bug#75394] [PATCH v14 0/2] Add jpm.
Date: Tue, 07 Jan 2025 09:15:41 +0200 [thread overview]
Message-ID: <877c77ccwy.fsf@gmail.com> (raw)
In-Reply-To: <87frlv721h.fsf@gmail.com> (Suhail Singh's message of "Mon, 06 Jan 2025 22:09:30 -0500")
Suhail Singh <suhailsingh247@gmail.com> writes:
> "jgart" <jgart@dismail.de> writes:
>
>> Do you intend to contribute a janet-build-system after this?
>
> Not being a janet user, likely not any time soon. I wasn't even
> intending to contribute jpm, I was simply helping review Omar's
> submission. Omar had, at one point however, mentioned a
> janet-build-system [1].
>
Yes, Thanks Suhail, your reviews helped me alot. This was my first
contribution to guix and I learned alot from it.
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.
>> 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?
> [1]: <https://issues.guix.gnu.org/72925#12>
Many Thanks to all,
Omar Bassam
next prev parent reply other threads:[~2025-01-07 7:16 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 [this message]
2025-01-08 15:30 ` Suhail Singh
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=877c77ccwy.fsf@gmail.com \
--to=omar.bassam88@gmail.com \
--cc=75394-done@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=suhailsingh247@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.