From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lirzin Subject: Re: Using cuirass to build your own manifest. Date: Sun, 12 Mar 2017 20:17:47 +0100 Message-ID: <877f3ui9t0.fsf@gnu.org> References: <87r328w58p.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43258) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cn904-0002gy-JL for guix-devel@gnu.org; Sun, 12 Mar 2017 15:17:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cn903-0001kD-Pr for guix-devel@gnu.org; Sun, 12 Mar 2017 15:17:52 -0400 In-Reply-To: <87r328w58p.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 08 Mar 2017 09:19:02 +0100") 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: Mathieu Othacehe Cc: guix-devel Hi, Mathieu Othacehe writes: > Here's a small tutorial on how to setup cuirass to build your own > manifest. Amazing work! :) > I see two major reasons for this kind of setup: > > * When you pull latest guix, hydra and bayfront may not have finished > building all the packages you use. > > * Hydra and bayfront won't build your custom packages. This is definitely a use case that I expect to be common so I agree with Ludo that would make sense to make a service for that. > To finish, the downsides of this setup are : > * You need to keep your manifest up-to-date on your build machine. Do you have ideas/suggestions on how to improve that? > * There are no easy ways to track cuirass status but to do some sql on > cuirass database. With the HTTP API that I hope will be implemented this summer, the situation would hopefully be better. Thank you for this tutorial. This is really useful given the current state of Cuirass documentation. ;) -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37