Re: What’s next?

Hi Chris, >> - File search. >> >> (I did work on it a year ago, it's stuck, would need help from people >> familiar with Cuirass.) > > That sounds interesting. What does it mean? Would it help me figure > out which commands come from which package? Yes, and more ;) > A feature I remember

Re: What’s next?

Finally finish my endlessh service. There's a version that works here: http://issues.guix.gnu.org/39136 But it runs as root and IS NOT containerized. P.S. Also there were some really great suggestions in the previous emails! -- Joshua Branson (joshuaBPMan in #guix) Sent from Emacs and

Re: bug#47897: [PATCH] substitutes: Don't cache negative lookups or transient errors.

Hi, Christopher Baines skribis: > The patches you've sent look good. Pushed as 938ffcbb0589adc07dc12c79eda3e1e2bb9e7cf8 (I was generous and lowered ‘%narinfo-negative-ttl’ to 10mn :-)). Thanks, Ludo’.

Re: unifying mcron and shepherd, service woes, improvements

On Sat, May 15 2021, raingloom wrote: > 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 please!

Re: unifying mcron and shepherd, service woes, improvements

On 5/15/21 12:59 PM, Ludovic Courtès wrote: raingloom skribis: Or is everyone else happy with the current design and it's just me who can't use Shepherd properly?  I think it’s fair to say it’s rough on the edges. :-) One thing that’s on the to-do list is switching to a real event loop in

Re: unifying mcron and shepherd, service woes, improvements

On Sat, 15 May 2021 18:59:52 +0200 Ludovic Courtès wrote: > > Security could also be improved probably. Can we have an OCAP model? > > I feel like I don't know enough to say, so this mail is meant more > > as a conversation starter. > > I think “having an ocap model” sounds nice but also

Re: What’s next?

On Sat, 15 May 2021 23:24:41 +0300 Efraim Flashner wrote: > package-transformations applied to the operating-system field of the > os-config. > Gosh, yes please. I keep bumping into this while debugging services. Also: * substitutes over bittorrent might be cool. * split packages more,

[spitball] integrating analyzers into build systems

Would it make sense to run analyzers like Infer or MyPy at build time? Maybe have something like --with-debug, so if there is an analyzer-log output, only then is Infer ran? In theory these tools are more useful for developers, but it's still potentially useful to independently analyze our

Re: What’s next?

Pierre Neidhardt writes: > Hi, > > Off the top of my head: > > - Optimize the man page database update during profile builds. > > - File search. > > (I did work on it a year ago, it's stuck, would need help from people > familiar with Cuirass.) That sounds interesting. What does it mean?

Re: What’s next?

On Sat, 2021-05-15 at 19:47 +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): What about Hurd?

Re: What’s next?

On 2021-05-15, Ludovic Courtès wrote: > 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): • Add a "make dist" job to ci.guix.gnu.org to produce prerelease source tarballs.

Re: GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released)

On 2021-05-16, Maxim Cournoyer wrote: > Yes, thank you Simon and Leo for the help with the release! I felt less > lonely :-). I've learned that producing a release can easily take 2-3 > weeks even in good conditions (e.g., not many blockers to fix). I'd > suggest anyone (myself included :-))

Re: What’s next?

Ludovic Courtès schreef op za 15-05-2021 om 19:47 [+0200]: > 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): [...] Distributing substitutes over IPFS. The original

GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released)

Hello, Ludovic Courtès writes: > 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

Re: What’s next?

Hi, Off the top of my head: - Optimize the man page database update during profile builds. - File search. (I did work on it a year ago, it's stuck, would need help from people familiar with Cuirass.) - A GUI. https://gitlab.com/daym/guix-gui.git seems to be a good starting point.