From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Add rubygems updater.
Date: Fri, 1 Jan 2016 10:28:03 +0100 [thread overview]
Message-ID: <20160101092803.GA19934@thebird.nl> (raw)
In-Reply-To: <56863869.6080501@uq.edu.au>
On Fri, Jan 01, 2016 at 06:27:21PM +1000, Ben Woodcroft wrote:
> Phew, you almost beat me to the first patch of the year there Pjotr..
Mine is trivial ;)
> It seems there's 30 packages to be updated, out of the 107 in
> ruby.scm. Going through each of these individually seems a little
> tedious, can we do them in bulk somehow or do they have to be
> committed individually? Building and testing all packages that
> require these packages would be a start - is there any way to list
> all dependent packages?
>
> gnu/packages/ruby.scm:2807:13: ruby-cutest would be upgraded from
> 1.2.2 to 1.2.3
> gnu/packages/ruby.scm:333:13: ruby-rspec-mocks would be upgraded
> from 3.2.1 to 3.4.0
(etc)
I don't think it is a good idea to automatically update
packages. Reason being that packages should be updated by someone who
is actively using that new version. Automated tests are one thing,
real user feedback another. Not to mention that many gems don't have
tests ;).
What is useful is to generate (export) an updated package using the
old one as an input. Or show a diff of version + SHA. That way it
becomes reasonably easy to update packages.
Pj.
next prev parent reply other threads:[~2016-01-01 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 8:27 [PATCH] Add rubygems updater Ben Woodcroft
2016-01-01 9:28 ` Pjotr Prins [this message]
2016-01-01 11:18 ` Ben Woodcroft
2016-01-01 11:42 ` Pjotr Prins
2016-01-01 18:17 ` Ludovic Courtès
2016-01-02 0:11 ` Ben Woodcroft
2016-01-02 20:54 ` Ludovic Courtès
2016-01-03 0:50 ` Ben Woodcroft
2016-01-03 14:06 ` Ludovic Courtès
2016-01-05 13:57 ` Ben Woodcroft
2016-01-05 14:56 ` Ricardo Wurmus
2016-01-08 18:18 ` Ludovic Courtès
2016-01-02 3:43 ` Pjotr Prins
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=20160101092803.GA19934@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=b.woodcroft@uq.edu.au \
--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).