Re: What’s next?

Hi Ludovic, Those are all good ideas, but to be brief: +1 for core-updates & newer GCC. Some other things I'd like to see that seem achievable in a 4-6 months time frame: * Add .deb and .rpm formats for 'guix pack'. * Better Texlive importer * Easier way to debug (guix debug package) -> leaves

Re: branch master updated: gnu: Add emacs-wucuo.

Hello, Mathieu Othacehe writes: > Hello Chris, > >> The n on this line means that this package can't be built, and also >> breaks the linter. >> >> I've removed the n in fd2abc2a51e2cc39ac67dcef1d21a8037147e798. > > It also broke Cuirass master evaluation. Doh. Sorry, my CTRL key is failing me.

Re: branch master updated: gnu: Add emacs-wucuo.

Hello Chris, > The n on this line means that this package can't be built, and also > breaks the linter. > > I've removed the n in fd2abc2a51e2cc39ac67dcef1d21a8037147e798. It also broke Cuirass master evaluation. Thanks for fixing it, Mathieu

Re: branch master updated: gnu: Add emacs-wucuo.

guix-comm...@gnu.org writes: > This is an automated email from the git hooks/post-receive script. > > ngz pushed a commit to branch master > in repository guix. > > The following commit(s) were added to refs/heads/master by this push: > new bb94429 gnu: Add emacs-wucuo. > bb94429 is describ

Re: What’s next?

On Sat, May 15, 2021 at 07:47:19PM +0200, Ludovic Courtès wrote: > Hello Guix! > > So, now that 1.3.0 is out the door, what’s next?! > > Here’s my wish list of things that look achievable within 4 to 6 months > (I hope to help on some of these): > > • Merging Guix Home. > > • Completing and

Re: Help me create a janet-build-system

Am Samstag, den 15.05.2021, 15:25 -0400 schrieb Jack Hill: > Leo, > > Thanks for your reply > > On Sat, 15 May 2021, Leo Prikler wrote: > > > Your code imports (guix utils), but (guix utils) is not present > > within > > the module closure present at build time. > > Did you mean (guix build util

Re: Help me create a janet-build-system

Leo, Thanks for your reply On Sat, 15 May 2021, Leo Prikler wrote: Your code imports (guix utils), but (guix utils) is not present within the module closure present at build time. Did you mean (guix build utils)? I used cc-for-target and cxx-for-target from (guix utils). Where would I add (

What’s next?

Hello Guix! So, now that 1.3.0 is out the door, what’s next?! Here’s my wish list of things that look achievable within 4 to 6 months (I hope to help on some of these): • Merging Guix Home. • Completing and consolidating Disarchive support (see ): cont

Re: Bringing substitutes from the Guix Build Coordinator to users

Ludovic Courtès writes: > That all sounds like a plan! > > Christopher Baines skribis: > >> There's a few intertangled things, but the main question is, if bayfront >> can be a source of substitutes, what's the path to actually have that >> benefit users? > > One way it’ll benefit everyone is b

Re: unifying mcron and shepherd, service woes, improvements

Hi! raingloom skribis: > Just throwing this out there: > mcron is basically a very simple service manager, so, why not just move > all its timer functionality into shepherd (like systemd's timer units) > and then we can have a unified way to manage and debug services. Yes, we could—see below.

Re: Cuirass accessibility

Hi Mathieu, Mathieu Othacehe skribis: > I have made the report public here[3]. Although I have already applied a > bunch of accessibility related fixes, there's still some work left. The > report if full of interesting teachings, and if some people want to join > me, they are more than welcome :

Re: GNU Guix 1.3.0 released

Hi! Maxim Cournoyer skribis: > We are pleased to announce the release of GNU Guix 1.3.0! Yay, congrats everyone! Kudos Maxim for taking responsibility for the whole process! Now you know what can be improved :-) and I’m interested in helping make the process smoother. There’s no rush, but we

Re: Bringing substitutes from the Guix Build Coordinator to users

Hello! That all sounds like a plan! Christopher Baines skribis: > There's a few intertangled things, but the main question is, if bayfront > can be a source of substitutes, what's the path to actually have that > benefit users? One way it’ll benefit everyone is by feeding build/reproducibility

Re: Cuirass accessibility

On Thursday, May 13, 2021 7:07 PM, Mathieu Othacehe wrote: > Hello, > > As part of the Cuirass NLNet grant[1], the website at > https://ci.guix.gnu.org has been audited by the Accessibility > Foundation[2]. That's nice. > I have made the report public here[3]. Although I have already applied a

Re: Free software telemetry and the Guix System

Hi all, On +2021-05-14 16:52:25 -0400, Leo Famulari wrote: > On Fri, May 14, 2021 at 06:55:34PM +, Cook, Malcolm wrote: > > > If these claims are true, then I think this is quite satisfactory for > > > our purposes. I wouldn't even object to enabling the telemetry code via > > > the CMake buil

Re: Free software telemetry and the Guix System

Also just to note, guix already has software in it with telemetry. Ipfs. Its disable by default though.On May 14, 2021 8:12 PM, Mark H Weaver wrote: > > Hi, > > Bone Baboon writes: > > What types of telemetry in free software programs are compatible with > > the Guix System? > > The relevan

Re: Help me create a janet-build-system

Am Samstag, den 15.05.2021, 01:07 -0400 schrieb Jack Hill: > Greetings Guix, > > I'm working on creating a build system for Janet [0] modules. This is > my > first time working with build systems, and while I have a much > better > understanding than when I started, I still don't understand it f