From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathieu Othacehe <m.othacehe@gmail.com>
Subject: Re: Building guix-modular with cuirass
Date: Wed, 02 May 2018 15:52:25 +0200
Message-ID: <876046412e.fsf@gmail.com>
References: <87a7tpc8vw.fsf@gmail.com> <87po2gyhem.fsf@gnu.org>
	<87r2mwk0o7.fsf@gmail.com> <878t93nlha.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48447)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.othacehe@gmail.com>) id 1fDsBO-00030h-OS
	for guix-devel@gnu.org; Wed, 02 May 2018 09:52:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.othacehe@gmail.com>) id 1fDsBJ-0001as-9f
	for guix-devel@gnu.org; Wed, 02 May 2018 09:52:34 -0400
In-reply-to: <878t93nlha.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>


Hey,

> In the near future, I want ‘guix pull’ to install a ‘guix’ binary as
> opposed to simply dropping a bunch of modules in ~/.config/guix/latest.
> At that point we won’t have this kind of problem anymore.

On the same topic, as I explained in a previous email
(https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00222.html) my
main use-case for cuirass is to evaluate my manifest and build the
corresponding packages.

I could use 'cuirass-jobs' procedure and set arguments to (#:arguments
(subset . "my-package-1" "my-package-2" ...)). The drawback of this
approach is that everytime the manifest is updated, a reconfigure of
cuirass service is needed to update the package list.

I'd like to have an upstream mecanism were cuirass evaluates a local
manifest file (or even better take it from a git repository), an build
all the corresponding packages. The only configuration input from the
user would be the path of his manifest.

My first idea would be to add a piece of code in
build-aux/hydra/build-manifest.scm that would pull a manifest specified
as an argument, evaluates the packages it contains and feed it to
cuirass but that sounds a bit hacky.

Any better idea ?

Thanks,

Mathieu