Andy Wingo writes:
> * libguile/init.c (scm_i_init_guile): Install the SIGSEGV handler unless
> GUILE_INSTALL_SIGSEGV_HANDLER is 0.
> * libguile/loader.c
> (scm_maybe_throw_exception_for_mutation_of_read_only_data): New public
> function.
> (sigsegv_handler): New helper.
> (scm_install_
Andy Wingo writes:
> Christopher Webber asks about breakage due to version skew between peer
> channels and channels and Guix itself. I think I would like to just
> ignore this problem for now: if you add channels and things break
> somehow due to an update in Guix or an update in some channel, t
Hi :)
Thanks all for review; comments and suggestions very welcome. Choosing
this message to reply to.
On Sun 02 Apr 2017 01:05, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> (1) Install Guix as a user. (This needs to be easier.)
>> (2) guix channel add potluck https:/
On Fri 31 Mar 2017 23:41, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Fri 31 Mar 2017 13:33, l...@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
;; These can only form part of a safe binding set if no mutable
;; pair is exposed to the sandbox.
(define *mutat
* libguile/init.c (scm_i_init_guile): Install the SIGSEGV handler unless
GUILE_INSTALL_SIGSEGV_HANDLER is 0.
* libguile/loader.c
(scm_maybe_throw_exception_for_mutation_of_read_only_data): New public
function.
(sigsegv_handler): New helper.
(scm_install_sigsegv_handler): New public functi
Chris Marusich skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Beside, related to Chris’ comment, I’m a bit concerned about versioning
>> in such a widely distributed repo. The package graph in Guix has zero
>> degrees of liberty: every package is connected to other packages; every
>> Gui