From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0@n0.is Subject: Re: Policy to remove obsolete packages Date: Tue, 5 Feb 2019 21:31:53 +0000 Message-ID: <20190205213134.yluu4butrdrcy6uj@uptimegirl.lan> References: <20190204100318.208254da@alma-ubu> <87munbkvy8.fsf@gnu.org> <20190205111301.2070ec2d@alma-ubu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:45604) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gr8VL-0004N6-1C for guix-devel@gnu.org; Tue, 05 Feb 2019 16:43:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gr8KB-0007UC-S0 for guix-devel@gnu.org; Tue, 05 Feb 2019 16:32:14 -0500 Received: from aibo.runbox.com ([91.220.196.211]:44418) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gr8KA-0007HK-FN for guix-devel@gnu.org; Tue, 05 Feb 2019 16:32:10 -0500 Received: from [10.9.9.211] (helo=mailfront11.runbox.com) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1gr8K3-0007ZY-9h for guix-devel@gnu.org; Tue, 05 Feb 2019 22:32:03 +0100 Received: by mailfront11.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) id 1gr8K2-0003T2-1s for guix-devel@gnu.org; Tue, 05 Feb 2019 22:32:02 +0100 Content-Disposition: inline In-Reply-To: <20190205111301.2070ec2d@alma-ubu> 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" To: guix-devel@gnu.org Bjrn Hfling transcribed 846 bytes: > On Mon, 04 Feb 2019 23:52:47 +0100 > Ludovic Courtès wrote: > > > > (Note that, IIUC, in openSuSE a package can be broken and yet remain > > installable by users, because the last binary that was produced is > > still around.) > > We have guix pull --commit=..., inferiors, channels and time-travel, so > there are plenty opportunities to keep old states :-) There are many ways to keep it, but they are really sometimes just jumping through too many hoops. Or depending on what your idea of keeping old packages is. it should be easy, but it involves a good amount[1] of work to build a much older version with the otherwise almost-only recent,updating,master. To the point where you have to do the logical thing and look into which versions upstream or guix build around that time as dependencies and simply "freeze" all the dependencies in your package. 1: amount depending on what you are building There are other ways to handle obsolete packages, but I think they don't map to how guix works: a year or 2 back i experimented with a complete resructure of Guix, and packages got split up differently (one module per package mostly) leading to different kinds of problems and fixes. a separate repository with the prefix -wip holds all the unstable, obsolete, unfinished, etc packagesi (remotely comparable to how ports trees are handled, but not quiet like it[1]). That's the gist of it. just have a repository instead of dropping it from a tree. Once it's fixed up in the "wip" repository, move it back into the main repository. I can elaborate more on this if you want me to once I'm no longer sick. > Björn >