From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: [PATCH] Add rubygems updater. Date: Fri, 1 Jan 2016 10:28:03 +0100 Message-ID: <20160101092803.GA19934@thebird.nl> References: <56863869.6080501@uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aEw0T-00033q-7T for guix-devel@gnu.org; Fri, 01 Jan 2016 04:28:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aEw0Q-0007WH-0N for guix-devel@gnu.org; Fri, 01 Jan 2016 04:28:21 -0500 Received: from mail.thebird.nl ([95.154.246.10]:54304) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aEw0P-0007Vh-QY for guix-devel@gnu.org; Fri, 01 Jan 2016 04:28:17 -0500 Content-Disposition: inline In-Reply-To: <56863869.6080501@uq.edu.au> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ben Woodcroft Cc: "guix-devel@gnu.org" 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.