From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH] Add cufflinks. Date: Wed, 16 Sep 2015 22:07:01 +0200 Message-ID: <87eghy6sd6.fsf@elephly.net> References: <871tdycmtr.fsf@gnu.org> <20150916195644.GC3460@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55056) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcIzA-0005ki-9v for guix-devel@gnu.org; Wed, 16 Sep 2015 16:07:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZcIz9-0004ZE-Fb for guix-devel@gnu.org; Wed, 16 Sep 2015 16:07:20 -0400 In-reply-to: <20150916195644.GC3460@debian> 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: Andreas Enge Cc: guix-devel Andreas Enge writes: > On Wed, Sep 16, 2015 at 07:10:08PM +0200, Ludovic Courtès wrote: >> > +(define boost-1.55 >> > + (package (inherit boost) >> I would keep it next to ‘boost’. > > If it is just a temporary work-around that will disappear at the next release, > it might make sense to keep it as a private variable next to its use. Yes, that’s what I thought. I didn’t want to expose a public “boost-1.55” package only because a package in bioinformatics.scm needs that particular version. > Actually, boost-1.59.0 has been released on August 13. So the easiest > approach might be to wait for the core-updates merge, then update boost, > then add the new package. Oh, I didn’t know. That would be okay as well, I guess. ~~ Ricardo