GNU bug report logs - #56604
[PATCH 0/8] Update Clojure to 1.11.1.

Previous Next

Full log

View this message in rfc822 format

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ludovic Courtès <ludo <at> gnu.org>, Roman Scherer <roman.scherer <at> burningswell.com>
Cc: 56604-done <at> debbugs.gnu.org
Subject: [bug#56604] [PATCH 0/8] Update Clojure to 1.11.1.
Date: Thu, 1 Sep 2022 12:03:37 +0200

[Message part 1 (text/plain, inline)]

On 01-09-2022 11:09, Ludovic Courtès wrote:
>> I guess this is expected, since a change in a build system might affect
>> all packages being built with it. But I was wondering if there is a way
>> to force only building the packages specified on the command line. Does
>> such a thing exists?
> No, it doesn’t exist, because that would be building something
> different.  In this case, building everything that depends on
> ‘ant-build-system.scm’ is unavoidable.
>
>> I was wondering what is the most efficient way to quickly iterate on
>> changes to a build system, without recompiling the whole world for that
>> build system. How would you do that?
> There’s no ideal solution as you’ll have to recompile the world anyway.

It is possible, actually, to test it for a single package first 
(although without interaction with the command line). In the package you 
would like to test things with, use '=>' in #:imported-modules:

((this module)
 ((that module) => (local-file "customised-that-module.scm")))

and keep the original that/module.scm unmodified.

At least, something like that is done in 'build-program' in 
build-aux/build-self.scm -- I haven't tried it out for something like 
this myself.

Greetings,
Maxime

[Message part 2 (text/html, inline)]

[OpenPGP_0x49E3EE22191725EE.asc (application/pgp-keys, attachment)]

[OpenPGP_signature (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.