Hi,
Ludovic Courtès writes:
> Hi,
>
> Ricardo Wurmus skribis:
>
>> on a modern Guix System with Gnome we’re pulling in Python 2. That’s
>> because gtk uses lash, and lash (last commit was 14 years ago) comes
>> with Python bindings — for Python 2.
>>
>> I’d like to propose one of the
Hello Guix,
For the purpose of reporting at the RISC-V summit, the RISC-V
Foundation is collecting information about the status of software
project support for RISC-V. See the spreadsheet link at:
https://lists.riscv.org/g/tech-announce/message/190
I see that Guix is not currently listed
Ludovic Courtès writes:
> Therefore, I propose to apply the following patch, which leaves out a
Yes! The patch looks good. I‘m fine with that license.
Regards,
Florian
On 2022-11-28, Ludovic Courtès wrote:
> You might remember that I started long ago asking people who had
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no Front-Cover Texts, and no
Hello,
This is a heads up to let you know that the
%BASE-PACKAGES-DISK-UTILITIES public variable exported from (gnu system)
may be removed in the near future.
For the rationale and more details, see the proposed change [0].
[0] https://issues.guix.gnu.org/59661#1
Thanks,
Maxim
Am Mon, Nov 28, 2022 at 06:22:15PM +0100 schrieb Ludovic Courtès:
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no Front-Cover Texts, and no Back-Cover Texts¹.
>
> Simon, what do you
Hi,
Ludovic Courtès writes:
> Hello Guix!
>
> You might remember that I started long ago asking people who had
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no Front-Cover Texts, and
Hi,
On Mon, 28 Nov 2022 at 15:44, Simon Josefsson via "Development of GNU Guix and
the GNU System distribution." wrote:
> Yes, that makes sense. I'm not the best person to summarize it, but
> starting pointers if someone wants to take it further:
Well, it is somehow part of,
*
Hi,
>
> Simon, what do you think about emailing the authors of the “10 years of
> stories” post asking if they agree with the licensing? :-) No rush,
> though the sooner the more likely we are to get an answer.
I'm one of them.
You can use what I wrote with the license you prefer.
Consider it
Hello Guix!
You might remember that I started long ago asking people who had
contributed to the blog whether they would agree to licensing their work
under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts¹.
I did not get
On Sun, 27 Nov 2022 10:35:13 -0800
Vagrant Cascadian wrote:
> It also makes me wonder if "advanced" will stand the test of
> time. Someday Guix-style systems might just be status quo, and thus no
> longer advanced. Guix of course will likely evolve over time... maybe
> it will still hold
Hi,
Attila Lendvai writes:
>> The scenario you describe above should be possible above (there is a
>> debugger that supports breakpoints and single stepping). Now, it may
>> be, as you wrote, that inlining can lead breakpoints to never be hit, or
>> that there are bugs in this area. These
Thanks Liliana, zimoun, Ryan and Vagrant for feedback!
Ludovic Courtès writes:
> Or if we do want to explain more, then perhaps we need a list of
> features that would also include things like Docker/VM image generation,
> declarative home environments, etc. But that’s broader topic.
Yes,
> Do you have examples in mind of things you’d like to log and that would
> have helped you on a debugging journey?
the first thing that pops to my mind is the service start gexp's in shepherd:
they felt impossible to debug. i often was pretty much resorting to staring at
the code, and then
> The scenario you describe above should be possible above (there is a
> debugger that supports breakpoints and single stepping). Now, it may
> be, as you wrote, that inlining can lead breakpoints to never be hit, or
> that there are bugs in this area. These things should be fixed, I agree.
i'm
Hi,
On Mon, 28 Nov 2022 at 12:06, Ludovic Courtès wrote:
> Why doesn’t it work in ‘guix repl’? Because auto-compilation is
> disabled:
Ah, thanks. Well, maybe we could have an option to start “guix repl”
with debug mode available… even if it is really slow.
> I think we should identify
Hi,
On Mon, 28 Nov 2022 at 11:49, Ludovic Courtès wrote:
> Hi,
>
> zimoun skribis:
>
>> On Sat, 26 Nov 2022 at 12:11, Ludovic Courtès wrote:
>
> [...]
>
>>> Now, if you really want to extend the set of things recognized, you
>>> could write variant of ‘url-fetch’ that passes a different
Maxim Cournoyer writes:
> Hi Simon,
>
> zimoun writes:
>
>> Hi Maxim,
>>
>> On Mon, 21 Nov 2022 at 15:55, Maxim Cournoyer
>> wrote:
>>
>>> In practice since using breakpoints/a debugger to debug Guile code
>>> rarely works as intended (in my experience hacking on Guix!), we
>>> typically
Hello!
Vagrant Cascadian skribis:
> On 2022-11-26, Simon Josefsson via "Development of GNU Guix and the GNU
> System distribution." wrote:
>> I find use of the term 'advanced' wrt Guix confusing and even mildly
>> excluding, even though it is wide-spread. What is advanced about Guix?
>> Can I
Hi,
Attila Lendvai skribis:
> which reminds me that a project-wide logging infrastructure would also
> greatly elevate the guix debugging experience.
Do you have examples in mind of things you’d like to log and that would
have helped you on a debugging journey?
Ludo’.
Hi,
zimoun skribis:
> scheme@(guix-user)> ,break example
> Trap 2: Breakpoint at #.
> scheme@(guix-user)> (example #t)
> $2 = 20
I get this:
--8<---cut here---start->8---
$ guile
GNU Guile 3.0.8
Copyright (C) 1995-2021 Free Software Foundation, Inc.
Guile
Hi,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
>> Also, I think I mentioned before that I almost never use breakpoints on
>> Guile code—not because of some deficiency of the debugger, not (just)
>> because I’m silly or inexperienced, but because it’s rarely the right
>> tool
Hi,
zimoun skribis:
> On Sat, 26 Nov 2022 at 12:11, Ludovic Courtès wrote:
[...]
>> Now, if you really want to extend the set of things recognized, you
>> could write variant of ‘url-fetch’ that passes a different #:mirrors
>> argument to ‘built-in-download’. Maybe ‘url-fetch’ could have a
23 matches
Mail list logo
