From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: Updating a package Date: Mon, 23 Sep 2019 15:45:50 +0200 Message-ID: <20190923154550.28df1274@scratchpost.org> References: <87impji8uk.fsf@fnb.co.za> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/eiwEYeNyLhS2daYdrC049yp"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60281) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCOfM-0003ln-2C for guix-devel@gnu.org; Mon, 23 Sep 2019 09:46:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iCOfJ-0000V1-RG for guix-devel@gnu.org; Mon, 23 Sep 2019 09:46:11 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:44022) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iCOfJ-0000Rp-B4 for guix-devel@gnu.org; Mon, 23 Sep 2019 09:46:09 -0400 In-Reply-To: <87impji8uk.fsf@fnb.co.za> 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: Divan Santana Cc: Guix-devel --Sig_/eiwEYeNyLhS2daYdrC049yp Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Divan, On Mon, 23 Sep 2019 12:51:42 +0200 Divan Santana wrote: > ./pre-inst-env guix build emacs-exwm > Should I do this after updating a package? make check to check all tests > pass? In this case not really--since "make check" tests guix the package manager. You didn't change the package manager, so it wouldn't help. >Or rather the CI does that? The CI does that and then it also builds all the other packages, not just guix the package manager. > Secondly, how do I go about testing this package on my system (laptop > running guix) to see if the updated package actually works? ./pre-inst-env guix package -i emacs-exwm The package is then installed into your profile and you can just use it like any other packages installed in your profile. > I've done this in channels.scm >=20 > (list > (channel > (name 'guix) > (url "https://gitlab.com/divansantana/guix/") > (branch "master"))) >=20 > And then updated to my fork, though not sure if that is the best way. That would work as well--but sounds like a lot of work. It is nicer to do it your way if you want to *keep* your package across updates if it doesn't make it into the main repository. Otherwise I don't think your way gives you any advantage over just installing the package. --Sig_/eiwEYeNyLhS2daYdrC049yp Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl2IzI4ACgkQ5xo1VCww uqUcWQf/VuaGuiVMKOR2bnOx2kZsfGoWoZM0058bJke2RcgXqeWAkVkBWhAHkJqG YVBMauqUERUC6fh97p6u3f7CeM01S9fnNwz8h3GzO5RkIQVVM/BArsYX81b/Qz2w BI8vZICui7XqBfUde6+iascW4FFbSlO0bYXDTz7FNBJBtwqoYMDTWp5UYPuBmBi9 BKSLOjWOgK+mO8ziCMrakYSHhwbOVeQAy9Txzn74baV+z0KVsbR3Jccym38+zExS LR4N85fKYP2nltRdo7LJ2TFHjIDeuP5R5N0M3fgj74wXCmR5AZagrMVnF7ruBPs6 3jAPQ4xcF2xfhk9Xjz38mNsQfdJDlQ== =APtq -----END PGP SIGNATURE----- --Sig_/eiwEYeNyLhS2daYdrC049yp--