Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi! jgart skribis: > This is because each of those "CLI calls" end up running `(exit 0)` > at the end in some form or another. Note that Guile’s ‘exit’ throws a ‘quit’ exception, which can be caught. Ludo’.

Re: guix refresh to a specific version?

Hi, Hartmut Goebel skribis: > I pushed my current working state to wip-import-version. The branch > also contains some patches from bug56295 (Add some Chicken eggs and > fix egg importer) and bug56318 (Fix github updater). Neat! > Basic ideas > > * Add a keyword argument „version“ to all “lat

Re: grafted package and CLI

Hi, zimoun skribis: > Or even, it can be confusing: > > $ guix shell curl@7.79.1 -- curl --version > curl 7.84.0 (x86_64-unknown-linux-gnu) libcurl/7.84.0 GnuTLS/3.7.2 > zlib/1.2.11 libidn2/2.3.1 nghttp2/1.44.0 > Release-Date: 2022-06-27 > [..] > > The issue is n

Re: Julia packages on build farms?

zimoun skribis: > (use-modules (guix build-system julia) > (guix packages) > (guix profiles) > (gnu packages)) > > > (manifest > (map package->manifest-entry > (fold-packages >(lambda (package result) > (if (eq? (package-build-system

Re: ’guix package --export-manifest’ using ’@version’?

Hi, zimoun skribis: > $ guix package -p gnu/store/vmn2b3cmfwf250i65rgvkamyr4971q7m-profile \ >--export-manifest > ;; This "manifest" file can be passed to 'guix package -m' to reproduce > ;; the content of your profile. This is "symbolic": it only specifies > ;; package names. To repro

Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi Ludo', On +2022-07-07 09:31:34 +0200, Ludovic Courtès wrote: > Hi! > > jgart skribis: > > > This is because each of those "CLI calls" end up running `(exit 0)` > > at the end in some form or another. > > Note that Guile’s ‘exit’ throws a ‘quit’ exception, which can be caught. Any possible

Re: First guix pull is too costly

Hello Ludo’ and Simon, Ludovic Courtès writes: [...] > Does ‘git clone’ do a better job than libgit2/Guile-Git (which is what > ‘guix pull’ uses) in case it gets disconnected while fetching the repo? > Is it able to resume when libgit2 isn’t? > > (I’d be surprised, but I don’t know.) AFAIU `gi

Re: Building, packaging and updating Guix with confidence

Josselin Poiret writes: > In the second case, I am in the process of adding a very simple Guile C > extension to Guix that only requires to wrap a simple libc function. > The C code itself took approx. 5% of my time on it, while adding the > magical invocations for the Autotools took 35%, and no

Re: ’guix package --export-manifest’ using ’@version’?

Hi, On Thu, 07 Jul 2022 at 09:57, Ludovic Courtès wrote: > (Nitpick: it *is* stateless, in the sense that it only depends on Guix > itself, not on the state of the machine where it is being run.) I will not argue about what we call state here. :-) > ‘--export-manifest’ emits a comment (shown

Re: grafted package and CLI

Hi, On Thu, 07 Jul 2022 at 10:00, Ludovic Courtès wrote: > Usually, when the replacement is a different version, we make it public, > so it also shows up in ‘guix package -A’. It’s just a convention, but > it’s probably good enough? About “guix package -A”, we cannot do more, so let say it is

Re: [EXT] Please reply: License of your contributions to the blog at guix.gnu.org

Hi, Sorry, I haven't been paying attention to mailing lists lately. I agree with CC-BY-SA 4.0 and GFDL 1.3+ dual-licensing for my contributions to the Guix blog. - Dave On Mon, Jul 4, 2022 at 9:56 AM Ludovic Courtès wrote: > Hello Danny, David, and Laura! > > I hope this message finds you wel

Re: Building, packaging and updating Guix with confidence

Hello, Zhu Zihao writes: > If your foreign function use case is very trivial? Why not give Guile > dynamic FFI a try? That could be another option, but I'd like to have autoconf be able to detect whether the target supports things like posix_spawn and getrlimit, which I use in the code. > It's

Re: grafted package and CLI

zimoun skribis: > Aside, the convention is to make the replacement public for different > versions, so my naive question is: why not hide the replaced version? You mean hide with the ‘hidden?’ property? Good question. There’s probably little point in exposing the original (replaced) version, s

Re: ’guix package --export-manifest’ using ’@version’?

zimoun skribis: > On Thu, 07 Jul 2022 at 09:57, Ludovic Courtès wrote: [...] >> It is a departure from traditional package managers, and admittedly >> surprising to newcomers. However, my take on this is that we should be >> very upfront about symbolic vs. exact reproducibility. We would mud

Re: grafted package and CLI

Hi, On Thu, 07 Jul 2022 at 17:09, Ludovic Courtès wrote: > You mean hide with the ‘hidden?’ property? I do not know what I mean. ;-) The replacement could have an ’hidden?’ property or not being ’define-public’. > Good question. There’s probably little point in exposing the original > (rep

Re: ’guix package --export-manifest’ using ’@version’?

Hi, On Thu, 07 Jul 2022 at 17:13, Ludovic Courtès wrote: > The “@X.Y” bit is added only when necessary to disambiguate the package > spec. So with today’s Guix, we have: Yes, but it is not what I reported initially [1]; it was: 1: https://yhetil.org/guix/868rp8zosc@gmail.com --8<