From: 宋文武 <iyzsong@envs.net>
To: Akib Azmain Turja <akib@disroot.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: New package request: aspell-dict-bn
Date: Thu, 05 Jan 2023 09:49:10 +0800 [thread overview]
Message-ID: <87fscp4up5.fsf@envs.net> (raw)
In-Reply-To: <87sfgsqk63.fsf@disroot.org> (Akib Azmain Turja's message of "Tue, 03 Jan 2023 11:08:52 +0600")
Akib Azmain Turja <akib@disroot.org> writes:
> I didn't modify any Guix files. I put that in a file (along with
> supporting forms) and passed the file to "guix package".
>
> I have the Guix repository (as left by "guix pull"), but how can I test
> my changes?
Hello, The guix manual (info guix or better viewed in emacs) has
a "Contributing" section talk about how to do this. Basically:
1. git clone the guix repository.
2. run bootstrap, configure and make
3. modify the correct source file
4. test it with ./pre-inst-env guix
5. git commit and git format-patch
6. send the patch to guix-patches mailing list
I think the checkout from "guix pull" can be used with "git worktree"
with some care, but I usually use a seperated git clone for contributing.
Hope this helps!
prev parent reply other threads:[~2023-01-05 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 17:41 New package request: aspell-dict-bn Akib Azmain Turja
2023-01-03 1:35 ` 宋文武
2023-01-03 5:08 ` Akib Azmain Turja
2023-01-05 1:49 ` 宋文武 [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fscp4up5.fsf@envs.net \
--to=iyzsong@envs.net \
--cc=akib@disroot.org \
--cc=help-guix@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).