From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Video Documentation for GNU GUIX (an Outreachy project)
Date: Mon, 29 Oct 2018 21:25:33 +0100 [thread overview]
Message-ID: <20181029212533.1608660a@alma-ubu> (raw)
In-Reply-To: <CA+H0LRMWb=T6W8KBTJ7ENG2A6t3b8GPY-vAApty+c1=D+VUtZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Hi Lakshmi,
On Tue, 30 Oct 2018 01:33:57 +0530
Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com> wrote:
> Hi Gábor,
> I just tried to import a package called 'weights' from cran
> repository. Its a package related to weighting and weighted
> statistics. I am attaching the definition package with this mail.
> Please find the attachment. In the next step I understand that we are
> suppose to store this in a file in the Guix store tree. I'm not sure
> about how to proceed with this step. Is it like pushing to git ?
"Pushing" would be only the final step. But that is only allowed for
registered developers.
To start: Follow the instructions in section 7 of the documentation:
https://www.gnu.org/software/guix/manual/en/guix.html#Contributing
To summarize it, you need to clone the git sources and then add your
package definition to the gnu/packages/cran.scm file, commit your
changes with a commit message as explained in section 7.5 (Submitting
Patches). Finally instead of pushing, you generate a patch file with
`git format-patch` and send it to the patches tracker.
Does that sound reasonable?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-10-29 20:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+H0LRPUfE=LmSETuasan3bEjEkGPXRFoE5Qrd-9G8DYO8buTQ@mail.gmail.com>
2018-10-17 6:45 ` Video Documentation for GNU GUIX (an Outreachy project) Björn Höfling
2018-10-17 8:11 ` Gábor Boskovits
2018-10-18 9:22 ` Lakshmi Prasannakumar
2018-10-18 11:46 ` Björn Höfling
2018-10-18 11:52 ` Gábor Boskovits
2018-10-18 12:37 ` Lakshmi Prasannakumar
2018-10-18 13:00 ` Gábor Boskovits
2018-10-23 12:34 ` Lakshmi Prasannakumar
2018-10-23 18:22 ` Gábor Boskovits
2018-10-29 9:25 ` Gábor Boskovits
2018-10-29 18:12 ` Lakshmi Prasannakumar
2018-10-29 19:57 ` Björn Höfling
2018-10-29 20:18 ` Lakshmi Prasannakumar
2018-10-29 20:27 ` Björn Höfling
2018-10-29 20:40 ` Lakshmi Prasannakumar
2018-10-29 20:58 ` Gábor Boskovits
2018-10-30 18:20 ` Lakshmi Prasannakumar
2018-10-31 4:45 ` Lakshmi Prasannakumar
2018-10-31 4:46 ` Lakshmi Prasannakumar
2018-10-31 7:18 ` Gábor Boskovits
2018-10-31 7:20 ` Gábor Boskovits
2018-10-31 8:32 ` Gábor Boskovits
2018-11-01 17:01 ` Lakshmi Prasannakumar
2018-11-01 17:36 ` Gábor Boskovits
2018-11-01 17:48 ` Lakshmi Prasannakumar
2018-10-29 20:03 ` Lakshmi Prasannakumar
2018-10-29 20:25 ` Björn Höfling [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=20181029212533.1608660a@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=lakshmiprasannakumaran@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).