all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Ricardo Wurmus <rekado@elephly.net>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Per-package updaters?
Date: Tue, 27 Dec 2016 09:48:54 +1000	[thread overview]
Message-ID: <6238646e-d115-3b5c-c266-d6aa8f679cf6@uq.edu.au> (raw)
In-Reply-To: <87o9zyka6c.fsf@elephly.net>

Hi Ricardo,


On 27/12/16 01:00, Ricardo Wurmus wrote:
> Hi Guix,
>
> we have a couple of generic package updaters (CPAN, CRAN, Bioconductor,
> Github, GNU, etc), but they don’t nearly cover all of our packages.  I
> wonder if we should add one-off updaters for individual packages that
> don’t fall into any of the generic classes of updaters.
>
> Another question is how to implement them.  Would there be another
> optional field in package expressions containing a Guile script to run
> to determine updates for the current package?
>
> What are your opinions on this?
How about we piggy-back on the good work of others, by putting a 
declaration in the package definition that the package has sister 
packages in other package managers? This would involve a level of 
munging of the other packager's versions, but this seems not difficult 
for well disciplined numbering schemes.

ben

  reply	other threads:[~2016-12-26 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 15:00 Per-package updaters? Ricardo Wurmus
2016-12-26 23:48 ` Ben Woodcroft [this message]
2016-12-31  0:29 ` Ludovic Courtès
2017-01-03  9:30   ` Efraim Flashner
2017-01-03 13:17     ` 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=6238646e-d115-3b5c-c266-d6aa8f679cf6@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.