unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: anonymiss <ng_prism@protonmail.ch>
To: guix-devel <guix-devel@gnu.org>
Subject: getting started test-building packages without breaking the system profile?
Date: Mon, 07 Dec 2015 12:54:53 -0500	[thread overview]
Message-ID: <SzdaY9jUGeTiHjuINleo4vpveL8-0WfPmdKb-5qitRh9hBq4qMIJGsBMQWHRLWAQrB3xtmG5nUhBZlyKDJgCJw==@protonmail.ch> (raw)

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

Hi,

I've read https://www.gnu.org/software/guix/manual/html_node/Packaging-Guidelines.html and I am done with the gnunet-gtk.scm, at least as far as I can go without testing.
My question is, do I check out the guix.git for testing the package with
./pre-inst-env guix build $pkg-name --keep-failed
or what is the general recommended process for this?
I know I can even setup VMs within guix with guix, but I just started and need some pointers.


--anonymiss
-----------------------------------------------
Email is public and violates our right for secrecy of correspondence.
Talk to me in private:
http://loupsycedyglgamf.onion/anonymiss/
irc://loupsycedyglgamf.onion:67/anonymiss
https://psyced.org:34443/anonymiss/

If you want Email like communication which respects
your privacy and rights and is secure without requiring you to
learn complicated tools, use bitmessage:
(public) bitmessage: BM-2cSj8qEigE3CMaLU3CwPZf7T3LvzvnttsC

my vcard (sort of): http://krosos.sdf.org

[-- Attachment #2: Type: text/html, Size: 1572 bytes --]

             reply	other threads:[~2015-12-07 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 17:54 anonymiss [this message]
2015-12-07 18:26 ` getting started test-building packages without breaking the system profile? Leo Famulari
2015-12-07 18:49   ` anonymiss
2015-12-07 19:54     ` Leo Famulari
2015-12-07 20:25       ` anonymiss
2015-12-07 18:54 ` Andreas Enge
2015-12-07 19:11   ` anonymiss
2015-12-07 20:11   ` Leo Famulari

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='SzdaY9jUGeTiHjuINleo4vpveL8-0WfPmdKb-5qitRh9hBq4qMIJGsBMQWHRLWAQrB3xtmG5nUhBZlyKDJgCJw==@protonmail.ch' \
    --to=ng_prism@protonmail.ch \
    --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).