Hi Leo,
Leo Famulari skribis:
> Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
> killed almost immediately after it starts with signal 15. I confirmed
> the issue started with the Shepherd upgrade by bisecting our Git
> history.
>
> I can reproduce the issue from commit
>
Hi Guix!
l...@gnu.org (Ludovic Courtès) skribis:
> • Have a “channel” mechanism, similar to ‘nix-channel’, that would
> allow users to have several Guix variants available in parallel
> instead of just “latest”. Could work like this:
>
> guix channel add latest git://git.sv.gnu.o
DRAFT: Missing documentation for ~/.config/guix/channels.scm.
* guix/channels.scm: New file.
* Makefile.am (MODULES): Add it.
* guix/scripts/pull.scm: Use it.
(%self-build-file, %pull-version, build-from-source)
(whole-package-for-legacy, derivation->manifest-entry): Remove. These
now exist in a
* guix/self.scm (scheme-modules*): Move to...
* guix/discovery.scm (scheme-modules*): ... here. New procedure. Make
'sub-directory' an optional parameter.
---
guix/discovery.scm | 13 -
guix/self.scm | 7 ---
2 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/g
* guix/describe.scm: New file.
* Makefile.am (MODULES): Add it.
* gnu/packages.scm (%package-module-path): Honor 'package-path-entries'.
---
Makefile.am | 1 +
gnu/packages.scm | 22 --
guix/describe.scm | 73 +++
3 files changed, 88
Ludo, I am so ready to try this!
GUIX_PACKAGE_PATH is killing me though it got a lot better after
latest guix pull developments.
Tell me what to run.
Pj.
This isn't exactly pretty, and obviously a better long-term solution is
needed, but I wrote a quick shell script to at least partially addresses
some my biggest fears with guix pull...
Basically, it updates a git checkout, checks the signatures on the
commits, looking for the topmost signed commit
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
> Currently third-party channels are expected to provide nothing but
> package modules.
I'd like to say again that I have grave concerns that this could be the
death-knell for long-term innovation in Guix. It's likely that whenever
a change is p
Hi Mark,
Mark H Weaver skribis:
> I'd like to say again that I have grave concerns that this could be the
> death-knell for long-term innovation in Guix. It's likely that whenever
> a change is proposed that will break these third-party channels, there
> will be resistance, and efforts to prese
Hi Mark,
I'd like to say again that I have grave concerns that this could be the > death-knell for long-term innovation in Guix. It's likely that
whenever> a change is proposed that will break these third-party
channels, there> will be resistance, and efforts to preserve backward
compatibilit
10 matches
Mail list logo
