Am 15.11.2016 um 22:13 schrieb Leo Famulari:
> Hartmut, can you push this to the recently created "staging" branch?
Done.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
On Thu, Oct 13, 2016 at 10:12:01PM +0200, Ludovic Courtès wrote:
> Hartmut Goebel skribis:
>
> > * guix/build/cmake-build-system.scm (cmake-build-system): Set
> > environment variable CTEST_OUTPUT_ON_FAILURE to an non-empty value.
>
> It’s a good idea, but it
Am 17.10.2016 um 22:14 schrieb Ludovic Courtès:
> Once ‘core-updates’ is merged (hopefully in a few days), we could start
> a ‘staging’ branch and put changes that require between ~300 and ~1200
> rebuilds. The idea would be to close the branch much more quickly than
> core-updates (the changes
Hartmut Goebel skribis:
> Am 13.10.2016 um 22:12 schrieb Ludovic Courtès:
>> It’s a good idea, but it would entail a rebuild of 1,000+ packages. Can
>> you save it for the next big-rebuild cycle?
>
> No problem.
>
> Still have to learn what "next big-rebuild cycle"
Am 13.10.2016 um 22:12 schrieb Ludovic Courtès:
> It’s a good idea, but it would entail a rebuild of 1,000+ packages. Can
> you save it for the next big-rebuild cycle?
No problem.
Still have to learn what "next big-rebuild cycle" means. Is there a
branch for it?
--
Regards
Hartmut Goebel
|
Hartmut Goebel skribis:
> * guix/build/cmake-build-system.scm (cmake-build-system): Set
> environment variable CTEST_OUTPUT_ON_FAILURE to an non-empty value.
It’s a good idea, but it would entail a rebuild of 1,000+ packages. Can
you save it for the next
* guix/build/cmake-build-system.scm (cmake-build-system): Set
environment variable CTEST_OUTPUT_ON_FAILURE to an non-empty value.
---
guix/build/cmake-build-system.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/guix/build/cmake-build-system.scm
b/guix/build/cmake-build-system.scm