From: zimoun <zimon.toutoune@gmail.com>
To: Aniket Patil <aniket112.patil@gmail.com>, guix-devel@gnu.org
Subject: Re: Outreachy contribution getting started.
Date: Mon, 12 Oct 2020 14:41:27 +0200 [thread overview]
Message-ID: <86eem3vcp4.fsf@gmail.com> (raw)
In-Reply-To: <CAF-xJgt7=N1+5bnwSX=uR6K7Qkaa6R9PGrvWksO9iVuzMkg=Lg@mail.gmail.com>
Hey!
Welcome!
And thank you for your interest in Guix.
Have you currently running Guix?
If no, the easiest is to start with the package manager [1] using the
shell script installer (first Red note in [1] :-)). The package manager
works on any GNU/linux distribution and is not in conflict with the
distro package manager. Do not hesitate to ask on help-guix@gnu.org or
#guix if you hit any problem, the Guix folks are prompt for
answering. :-) Once you can run "guix <command>" [2], you can read how
to define a package [3]. BTW, give a look to the Perfect Setup [4] and
here [5] my config files if you need inspiration. ;-)
Well, if you have already used --- or currently using --- you can try
"guix import" or "guix refresh"; i.e., write your first package
contribution. Therefore, you need to read [6]. Again, do not hesitate
to ask on help-guix@gnu.org or #guix if you hit any problem.
To be concrete, I suggest to read [3, 7, 8, 9, 10, 11, 12] and try to
package something. Easy and good candidates for first packages are CRAN
or BioConductor packages:
guix import cran <pkg>
guix import cran -a bioconductor <pkg>
You can pick unpackaged one from the list [12]. Do not hesitate to ask
if you do not find an obvious one –– it should a good occasion to show
you “guix repl”. :-)
[1] http://guix.gnu.org/manual/devel/en/html_node/Binary-Installation.html#Binary-Installation
[2] http://guix.gnu.org/manual/devel/en/html_node/Getting-Started.html#Getting-Started
[3] http://guix.gnu.org/cookbook/en/html_node/Packaging-Tutorial.html#Packaging-Tutorial
[4] http://guix.gnu.org/manual/devel/en/html_node/The-Perfect-Setup.html#The-Perfect-Setup
[5] https://github.com/zimoun/my-conf
[6] http://guix.gnu.org/manual/devel/en/html_node/Contributing.html
7 : https://guix.gnu.org/manual/devel/en/guix.html#Defining-Packages
8 : https://guix.gnu.org/manual/devel/en/guix.html#Packaging-Guidelines
9 : https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-import
10: https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-refresh
11: https://guix.gnu.org/manual/devel/en/guix.html#Building-from-Git
12: https://bioconductor.org/packages/release/bioc/
All the best,
simon
prev parent reply other threads:[~2020-10-12 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 11:52 Outreachy contribution getting started Aniket Patil
2020-10-12 12:41 ` zimoun [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=86eem3vcp4.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=aniket112.patil@gmail.com \
--cc=guix-devel@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.
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).