unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: anonymiss <ng_prism@protonmail.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: getting started test-building packages without breaking the system profile?
Date: Mon, 7 Dec 2015 19:54:51 +0100	[thread overview]
Message-ID: <20151207185451.GA4064@debian> (raw)
In-Reply-To: <SzdaY9jUGeTiHjuINleo4vpveL8-0WfPmdKb-5qitRh9hBq4qMIJGsBMQWHRLWAQrB3xtmG5nUhBZlyKDJgCJw==@protonmail.ch>

On Mon, Dec 07, 2015 at 12:54:53PM -0500, anonymiss wrote:
> 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.

It would be better to add the package to the existing gnunet.scm (which also
makes it easier to test, as there is no need to register a new file in
gnu-system.am).

Is a separate package needed, or could the existing recipe be extended to
also build the gtk+ binaries? If there is no separate source, I think this
would be the preferred approach.

> 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?

This is how I work; in this way, you can provide a patch that applies
directly on top of master.

Andreas

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 17:54 getting started test-building packages without breaking the system profile? anonymiss
2015-12-07 18:26 ` 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 [this message]
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=20151207185451.GA4064@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ng_prism@protonmail.ch \
    /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).