From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Building guix-modular with cuirass Date: Thu, 10 May 2018 00:05:31 +0200 Message-ID: <87zi18wklw.fsf@gnu.org> References: <87a7tpc8vw.fsf@gmail.com> <87po2gyhem.fsf@gnu.org> <87r2mwk0o7.fsf@gmail.com> <878t93nlha.fsf@gnu.org> <876046412e.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fGXDK-00075t-7L for guix-devel@gnu.org; Wed, 09 May 2018 18:05:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fGXDJ-0002xI-AN for guix-devel@gnu.org; Wed, 09 May 2018 18:05:34 -0400 In-Reply-To: <876046412e.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 02 May 2018 15:52:25 +0200") 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@gnu.org" Hi! Mathieu Othacehe skribis: > 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 ? Perhaps we can make the package selection mechanism in build-aux/hydra/gnu-system.scm a bit more flexible and export the relevant procedures so you can write your own build-manifest.scm that would just be a few lines and otherwise reusing what gnu-system.scm already provides. How does that sound? Ludo=E2=80=99.