all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix package modif testing
Date: Wed, 27 Jul 2016 15:25:25 +0200	[thread overview]
Message-ID: <20160727132525.GB4819@solar> (raw)
In-Reply-To: <CAEwRq=oTw4_bR+F=_ApB=h4NBigG-=unwUkKCtwMhLvEh9A+Rw@mail.gmail.com>

On Wed, Jul 27, 2016 at 03:19:43PM +0200, Vincent Legoll wrote:
> It looks like this :
> https://www.gnu.org/software/guix/manual/guix.html#Building-from-Git
> is intended for people willing to hack on guix itself, but I want to hack
> at the package's definitions...

This is all the same, everything is tightly integrated.

> I want to test the pythondialog patch I posted in te other thread...
> How do you try modifications to packages that are already in the repo ?

Personally I just create another local git branch and make my
modifications there, in gnu/packages/....scm. In case things work out,
it is then trivial to create a patch (git commit + git format-patch)
and to send it to the list (you may even use git send-email, which
is in a separate output of the git package).

Andreas

  reply	other threads:[~2016-07-27 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 13:19 guix package modif testing Vincent Legoll
2016-07-27 13:25 ` Andreas Enge [this message]
2016-07-27 13:49   ` Alex Vong
2016-07-27 14:56     ` Vincent Legoll
2016-07-27 16:21       ` Andreas Enge
2016-07-27 16:37         ` Vincent Legoll
2016-07-27 17:01           ` Andreas Enge
2016-07-27 17:02             ` Andreas Enge
2016-07-27 17:19               ` Vincent Legoll
2016-07-27 19:03           ` Alex Vong
2016-07-28  7:11             ` Vincent Legoll
2016-07-28  9:15               ` Vincent Legoll
2016-07-28 12:51                 ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160727132525.GB4819@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.