unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Divan Santana <divan@santanas.co.za>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Updating a package
Date: Mon, 23 Sep 2019 15:45:50 +0200	[thread overview]
Message-ID: <20190923154550.28df1274@scratchpost.org> (raw)
In-Reply-To: <87impji8uk.fsf@fnb.co.za>

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

Hi Divan,

On Mon, 23 Sep 2019 12:51:42 +0200
Divan Santana <divan@santanas.co.za> 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
> 
> (list
>       (channel
>        (name 'guix)
>        (url "https://gitlab.com/divansantana/guix/")
>        (branch "master")))
> 
> 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.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-09-23 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 10:51 Updating a package Divan Santana
2019-09-23 13:45 ` Danny Milosavljevic [this message]
2019-09-24 18:02   ` Divan Santana

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=20190923154550.28df1274@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=divan@santanas.co.za \
    --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).