So if system-config-printer is an ugly python hack based on pycups, can we do better in guile? (pycups is 95,9% written in C) https://github.com/molefrog/cupsidity Is an alternative to pycups written
Hi, Danny Milosavljevic transcribed 15K bytes: I agree to some extent. From a daily usage perspective, it is not nice. Especially looking at it from where I originally started, slackware and slackwar
Hi, so bug#26941 (which is only tangentially related) has made me think about a long-standing usability wart of Guix: The verbosity of Guix messages is really off-putting for regular users. Ideally,
Hi Today I investigated a bit about this program. system-config-printer is a Red hat offspin that is essentially a quick python hack to be able to say "we have a desktop gui for printer configuration
Hello, Danny Milosavljevic <address@hidden> skribis: It should work (for local builds at least). Perhaps you also need --no-grafts? Or maybe there’s a bug. Sure, just look for in in /var/log/guix/d
Hi, I'm trying to get this to work but guix build --log-file foo doesn't seem to print the location of the build log in the failure case... Is it possible to get to it somehow? Apparently the log fil
Danny Milosavljevic <address@hidden> skribis: It was correct once upon a time. :-) Here’s the current one: <https://nim-lang.org/blog/2017/01/08/version-0160-released.html>. Ludo’.
Hi Danny, Danny Milosavljevic <address@hidden> skribis: Nice hack! I don’t think we should incorporate it just right now; I would prefer something that writes “building foo” or “downloading b
There's a bug I opened about adding an --only-substitutes option: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26608 Ludo seems to support it, so I guess really someone just needs to implement it. I
Is it possible to have `guix package' NOT build from source? I really hate it when big packages like icecat, epiphany, or libreoffice start building on my machine. It takes about a day for each one
I agree that Guix is too verbose by default. It would be sufficient if Guix told the user that it is building from source for some reason. Upon failure it can print the location of the build log. --
I agree. 'guix build' should be as verbose as it is now. It is actually very useful for detecting little things like missing dependencies or wrong configuration options when building a package. But I
Hello, Danny Milosavljevic <address@hidden> skribis: Agreed for these. Danny, your suggestions go a bit further than what I had in mind :-), which was to write (roughly) one progress line per item bu
And also the spinner integrated: diff --git a/guix/scripts/package.scm b/guix/scripts/package.scm index f050fad97..d9ac61122 100644 -- a/guix/scripts/package.scm +++ b/guix/scripts/package.scm @@ -46
And the spinner implementation: (define p (let ((index 0) (spinner-chars "|\\-/")) (define (spin) (set! index (+ index 1)) (if (>= index (string-length spinner-chars)) (set! index 0)) (display (array
Right, but my point was that new tools are unfamiliar and intimidating even to technical users. I might know how to use GCC, but I will still find the interface and output of another language's compi
Hi Leo, That's because even my huge xterm scrollback buffer doesn't contain it anymore. I couldn't include it because I never saw it in the first place - and I can't reach it anymore. I agree. guix b