unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Tracking upstream releases
Date: Sun, 25 Oct 2015 22:42:19 +0100	[thread overview]
Message-ID: <87eggik4lg.fsf@gnu.org> (raw)
In-Reply-To: <874mhj9v1s.fsf@gmail.com> (Alex Kost's message of "Thu, 22 Oct 2015 11:17:19 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2015-10-21 15:54 +0300) wrote:
>
>> Hello!
>>
>> We now have a number of importers, which is great, but so far we had no
>> support to update packages once they had been imported, even though most
>> of the code to do that already is in the importer.
>>
>> So commit 0a7c5a09 generalizes the upstream-tracking code from (guix
>> gnu-maintenance) a bit, such that we can then easily define “updaters”
>> based on the import code.  As an example, subsequent commits add an
>> updater for ELPA and one for CRAN.  The end result is:
>>
>>
>> $ ./pre-inst-env guix refresh -t cran -t elpa
>> gnu/packages/statistics.scm:819:13: r-testthat would be upgraded from 0.10.0 to 0.11.0
>> gnu/packages/emacs.scm:856:13: emacs-auctex would be upgraded from 11.88.6 to 11.88.9
>>
>> (When ‘-t’ is omitted, all the updaters are used.)
>
> Great!  What about instead of (or along with) "-t cran -t elpa", use a
> comma separated list as it is done in "guix lint --checkers=..."?

I agree it would be more consistent (I guess I was a bit lazy here…)
Would you like to make this change?  Otherwise I can give it a go.

Thanks,
Ludo’.

  reply	other threads:[~2015-10-25 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 12:54 Tracking upstream releases Ludovic Courtès
2015-10-21 13:17 ` Thompson, David
2015-10-21 17:03 ` Andreas Enge
2015-10-22  8:17 ` Alex Kost
2015-10-25 21:42   ` Ludovic Courtès [this message]
2015-10-27 19:00     ` [PATCH] refresh: Support comma separated updater types Alex Kost
2015-10-27 20:18       ` Ludovic Courtès
2015-10-28 18:54         ` Alex Kost

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=87eggik4lg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --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).