unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Jeremy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Failed to connect to guix daemon socket in pure env
Date: Fri, 21 Feb 2020 13:59:31 +0100	[thread overview]
Message-ID: <CAJ3okZ35MOZo5QCgBqyhMnH6N=zpwO9WJE3AyKB3jt9OP_zQzw@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ3KyLE=-62zDrQao3k=XLiODxkDOeCbPKbFManmVq_+0A@mail.gmail.com>

Hi Jeremy,

Let send you first contribution. ;-)

Well, now you should be to build your package, something like:

   guix build -f your-definition.scm

where the file your-defintion.scm contains the recipe of your package.

Then, the instructions about how to submit.

1. clone from savanah and go to the directory
2. guix environment --container guix --ad-hoc git git:sendemail emacs
3. ./bootstrap && ./configure --localstatedir=/var/ && make
4. add the definition in the file gnu/packages/emacs-xyz.scm
Do not forget: a) to add your name on the top (copyright) and b) check
the indentation (M-C-q using Emacs on the opening parenthesis of your
addition)
5. check it works, first by searching or showing it:
   ./pre-inst-env guix search emacs ac geiser
   ./pre-inst-env guix show emacs-ac-geiser
6. Build it and address the warnings
   ./pre-inst-env guix build emacs-ac-geiser
7. Verify the reproducibility
   ./pre-inst-env guix build emacs-ac-geiser --no-grafts --check -K
8. Lint and address the issue
   ./pre-env-inst guix lint emacs-ac-geiser

If everything is fine, let commit and submit. Look at other commit
messages to find inspiration :-) Roughly speaking:

  gnu: Add emacs-ac-geiser.

  * gnu/packages/emacs-xyz.scm (emacs-ac-geiser): New variable.

There is yasnippet for Emacs which eases the addition.

Last, use format-patch: git format-patch -n1.
And send it: git send-email --to=guix-patches@gnu.org 0001-Add-blablabla.patch

Maybe you need to configure your smtp in ~/.gitconfig:

[sendemail]
    smtpServer =
    smtpServerPort =
    smtpEncryption = tls
    smtpUser =
    smtpPass =


And if you are still motivated, you could add all the "first
contribution" process to the Cookbook. ;-)


Cheers,
simon

  reply	other threads:[~2020-02-21 12:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 23:33 Failed to connect to guix daemon socket in pure env Jeremy Korwin-Zmijowski
2020-02-20  0:17 ` zimoun
2020-02-20  7:53   ` Jeremy Korwin-Zmijowski
2020-02-20  7:54     ` Jeremy Korwin-Zmijowski
2020-02-20  8:13       ` Jeremy Korwin-Zmijowski
2020-02-20 10:10         ` zimoun
2020-02-21 12:59           ` zimoun [this message]
2020-02-22 10:26             ` Jérémy Korwin-Zmijowski
2020-02-20  0:25 ` zimoun

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='CAJ3okZ35MOZo5QCgBqyhMnH6N=zpwO9WJE3AyKB3jt9OP_zQzw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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).