From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Othacehe Subject: Re: Using cuirass to build your own manifest. Date: Mon, 13 Mar 2017 09:43:43 +0100 Message-ID: <87k27tsh1c.fsf@gmail.com> References: <87r328w58p.fsf@gmail.com> <877f3ui9t0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cnLa2-0001KG-Jf for guix-devel@gnu.org; Mon, 13 Mar 2017 04:43:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cnLZz-0007Qh-Cv for guix-devel@gnu.org; Mon, 13 Mar 2017 04:43:50 -0400 In-reply-to: <877f3ui9t0.fsf@gnu.org> 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 Lirzin Cc: guix-devel Hi, > Amazing work! :) Thank you ! >> 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? Well there is the option to pull a git repository containing the manifest with mcron. Or maybe drv-list procedure could do the git pull before loading the manifest ? > >> * 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. I read your plans for GSOC, I'm really eager to see the result :) Mathieu