Re: [PATCH] Add rubygems updater.

[Pjotr Prins]

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.