From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Vong Subject: Re: guix package modif testing Date: Wed, 27 Jul 2016 21:49:22 +0800 Message-ID: <877fc75gyl.fsf@gmail.com> References: <20160727132525.GB4819@solar> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45078) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bSPDO-0004Uq-Hh for guix-devel@gnu.org; Wed, 27 Jul 2016 09:49:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bSPDI-0004Js-PX for guix-devel@gnu.org; Wed, 27 Jul 2016 09:49:37 -0400 Received: from mail-pf0-x243.google.com ([2607:f8b0:400e:c00::243]:35050) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bSPDI-0004Jg-Im for guix-devel@gnu.org; Wed, 27 Jul 2016 09:49:32 -0400 Received: by mail-pf0-x243.google.com with SMTP id h186so1895157pfg.2 for ; Wed, 27 Jul 2016 06:49:32 -0700 (PDT) In-Reply-To: <20160727132525.GB4819@solar> (Andreas Enge's message of "Wed, 27 Jul 2016 15:25:25 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Vincent Legoll Cc: guix-devel Hi, Andreas Enge writes: > 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). > Same for me. Usually, I run "git pull" first to update the repo. Then, I build using "./boostrap && make -j`nproc`". After that, I changes the files in guix/gnu/packages/. Next, I test the changes by "./pre-inst-env guix lint foo" and "./pre-inst-env guix build foo". If the changes pass the lint and the build, run "git commit" and "git format-patch HEAD^". Finally, attach the patch and send the email. Notice all the commands is run with guix/ being the current working directory. Also, I am learning to use magit, so this is really the old approach I use. Hope this help. > Andreas Cheers, Alex