unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Jan <tona_kosmicznego_smiecia@interia.pl>, guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Fri, 18 Oct 2019 21:28:28 +0200	[thread overview]
Message-ID: <87ftjpyhsz.fsf@devup.no> (raw)
In-Reply-To: <20191018205608.45b264dc@kompiuter>

[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]

Hello Jan,

Jan <tona_kosmicznego_smiecia@interia.pl> writes:

> Hi all,
> It seems Jami package is outdated and unmaintained, so I would like to
> become a maintainer of the package.
> I know the basics of Guile Scheme and Guix System, I'm more or
> less familiar with how Jami works and what are its dependencies, but I
> don't know much about development, git or build systems.
> What are the things I need to learn to be able to start packaging?

Thank you for your interest in maintaining Jami!

You will need to learn the basics of git in order to make commits and
send patches.  You should also read this section of the manual:

https://guix.gnu.org/manual/en/guix.html#Building-from-Git

A typical workflow would go along these lines:

First time setup:
$ git clone https://git.savannah.gnu.org/git/guix.git
$ cd guix
$ guix environment guix
[env] $ ./bootstrap
[env] $ ./configure --localstatedir=/var
[env] $ make -j4 # adjust for number of cores on your machine

That will build the latest version of Guix locally.  Now you can use the
'./pre-inst-env' script to run guix operations from this directory.  You
should repeat the 'make' step when you have pulled or made other
changes, to pre-compile the Scheme modules.

Making changes to the repository:
$ ./pre-inst-env guix edit jami
$ [...hacking away...]
$ ./pre-inst-env guix build jami
(investigate build failures, repeat until it works)

Once you are happy with your changes, you should commit them and send a
patch to guix-patches@gnu.org:

$ git add -p
(press y on the hunks you wish to stage)
$ git commit # commit the staged changes
$ git send-email --to guix-patches@gnu.org -1 HEAD

Alternatively you can create a patch file with 'git format-patch -1
HEAD' and use your favourite mail user agent to send it.

Please don't hesitate to ask for help here or on the #guix IRC channel
if you get stuck on anything :-)

Hope this helps,
Marius

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-10-18 19:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke [this message]
2019-10-19  9:02   ` Pierre Neidhardt
2019-10-19 20:38     ` Jan Wielkiewicz
2019-10-19 20:52       ` Ricardo Wurmus
2019-10-19 22:37         ` Jan
2019-10-20 11:14           ` Ricardo Wurmus
2019-10-20 11:51           ` Pierre Neidhardt
2019-10-20 11:48       ` Pierre Neidhardt
2019-10-25 15:03         ` Pierre Neidhardt
2019-10-25 19:44           ` Jan Wielkiewicz
2019-10-26 10:12             ` Pierre Neidhardt
2019-10-26 23:24               ` Jan Wielkiewicz
2019-10-28  7:53                 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18   ` Pierre Neidhardt
2019-10-27 19:23     ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37   ` Pierre Neidhardt
2019-10-31 22:26   ` Marius Bakke
2019-11-01 12:01     ` Jan Wielkiewicz
2019-11-01 19:02       ` Pierre Neidhardt
2019-11-01 20:42         ` Jan Wielkiewicz
2019-11-02  9:38           ` Pierre Neidhardt
2019-11-03 16:37       ` Marius Bakke
2019-11-03 17:43         ` Jan
2019-11-03 18:06           ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01   ` Pierre Neidhardt
2019-11-01 23:16     ` Jan Wielkiewicz
2019-11-03 10:15       ` Pierre Neidhardt
2019-11-03 10:54         ` Jan Wielkiewicz
2019-11-04 10:02           ` Gábor Boskovits
2019-11-03 10:59         ` Jan Wielkiewicz
2019-11-03 17:07   ` Marius Bakke
2019-11-03 17:47     ` Jan
2019-11-03 18:12   ` Marius Bakke
2019-11-03 18:27     ` Jan
2019-11-03 18:52       ` Marius Bakke

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=87ftjpyhsz.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /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).