On Sat, Jan 14, 2023 at 11:07:23PM +0100, Ludovic Courtès wrote:
> Hello!
>
> Over the course of a few years, the size of our packages has apparently
> kept growing. Example:
>
> --8<---cut here---start->8---
> $ guix time-machine --commit=v1.2.0 -- size emacs
Hi,
On Mon, 16 Jan 2023 at 23:40, "jgart" wrote:
> What do you think if we would be able to give past generations a name?
Well, I think this would be difficult. And personally I do not have the
use case.
However, be able to locally Git tag and use this tag with “guix
time-machine” will be ver
Hi Paul,
On Mon, 16 Jan 2023 at 18:59, Paul Jewell via "Development of GNU Guix and the
GNU System distribution." wrote:
> guix system --switch-generation ... --delete-generation ...
>
> but I am reading into your comment that guix system does _not_ use
> SRFI-37, and therefore cannot combine
i have this, which uses guix when available, but works without it, too:
the entire file:
https://hub.darcs.net/hu.dwim/hu.dwim.environment/browse/bin/build-development-image.sh
it builds an executable SBCL image with every dependency of our project loaded.
we start it as an inferior for Slime.
Hey!
The last update was sent out in September [1], so 4 and a bit months
ago.
1: https://lists.gnu.org/archive/html/guix-devel/2022-09/msg00038.html
## Numbers
bordeaux.guix.gnu.org currently provides ~2 million nars, which take up
~8.3TiB to store.
Substitute availability is still reasonabl
Egun on!
Could you send the whole changeset to guix-patc...@gnu.org? That’ll
make sure (1) it doesn’t get lost, and (2) it’s tested by
https://qa.guix.gnu.org. (Use ‘git send-email’ for best results.)
Thanks,
Ludo’.
Hi Carl,
Carl Dong skribis:
> The paper is titled "Reproducible Containers”:
> https://dl.acm.org/doi/pdf/10.1145/3373376.3378519, featured by Meta in their
> post:
> https://developers.facebook.com/blog/post/2022/11/22/hermit-deterministic-linux-testing/
Interesting! Probably a sledgehamme
Hi,
Bruno Victal skribis:
> On 2023-01-09 10:51, Ludovic Courtès wrote:
>> Hello!
>>
>> mirai skribis:
>>
>>> An oddity of how nginx modules are packaged in guix is that they all place
>>> the .so file under /etc/nginx/modules which is an odd directory to place
>>> library object files.
>>
Hi,
Stephen Paul Weber skribis:
>>Once we update the ‘guix’ package, the daemon will no longer accept
>>‘url-fetch’ downloads with hash = #f.
>
> Ok. Is there something like (git-checkout) we can use that will work
> instead of an (origin) here for url downloads?
There’s in (guix transformati
Hello,
Simon Tournier skribis:
> Other said, build systems use some version for compiler and tools but
> Guix can also offer more recent versions for these very same compilers
> and tools. It leads to the issue when selecting the name of a compiler
> or tool (command line or manifest). The use
Hi,
Ryan Prior skribis:
> A free software project to look at for ideas is Mackup:
> https://github.com/lra/mackup
> Its strategy is unsophisticated: it moves your configuration files to a
> synchronized directory in Dropbox (or similar) and replaces it with a
> symlink. But it's got a great m
Maxim Cournoyer skribis:
> [polkit] is already using duktape by default on core-updates, so that
> particular one is solved.
That’s a much welcome improvement!
--8<---cut here---start->8---
$ guix size mozjs | tail -1
total: 264.8 MiB
ludo@ribbon ~/src/guix [
Hi,
Efraim Flashner skribis:
> I've made some progress on LLVM and I think I have a working LLVM that
> can be used as an input for mesa.
>
> (ins)efraim@3900XT ~$ du -sch
> /gnu/store/36kmnxmb1h8pxw0x71wril67fdvjx7ny-llvm-11.0.0/*
> 3.9M/gnu/store/36kmnxmb1h8pxw0x71wril67fdvjx7ny-llvm-11.0
Hi,
"pelzflorian (Florian Pelz)" skribis:
> Ludovic Courtès writes:
>> Over the course of a few years, the size of our packages has apparently
>> kept growing.
>
> Disregarding dependencies, most store items got slightly bigger. This
> is what I wrote at bug#58760 “Guix System iso too big for
Hi!
Maxim Cournoyer skribis:
> There are also many old-school catch/throw references too, so that makes
> it two! These can technically be handled using the new style mechanism
> too
Well, yes and no. The migration to from key+args (what ‘catch’ deals
with) to exception objects (à la SRFI-35
Hello,
Christopher Baines skribis:
> I merged the changes a few days ago, so this is just a quick message to
> say that the commit policy has changed. You can read the updated policy
> here:
>
>
> https://guix.gnu.org/en/manual/devel/en/html_node/Commit-Access.html#Commit-Policy
Nice, thanks
I like it.
> Egun on!
>
> Could you send the whole changeset to guix-patc...@gnu.org? That’ll
> make sure (1) it doesn’t get lost, and (2) it’s tested by
> https://qa.guix.gnu.org. (Use ‘git send-email’ for best results.)
Sure thing!
My email provider doesn't play well with git send-mail but I'll do it as
Hi,
Ludovic Courtès writes:
> Thoughts?
What if package variables in Guix were functions that accepted an
optional argument?
Each function could deliver any available version or a default, possibly
accompanied by a warning when the wanted version was not available.
Kind regards
Felix Lechne
Hi,
On lun., 16 janv. 2023 at 20:43, zimoun wrote:
> Now consider:
>
> $ guix shell -C emacs-minimal emacs-org -E TERM \
>-- emacs -q -l config.el \
>--eval "(require 'org-element)" \
>-f org-agenda
>
> Then press ’m’ and type: CLO
Hi Ludo,
On mar., 17 janv. 2023 at 17:09, Ludovic Courtès wrote:
>> For other cases, such issue is avoided by appending the suffix -next to
>> package name; as with ghc-next, python-numpy-next, emacs-next, etc.
>>
>> Personally, I find the -next trick useful because the package name
>> reflects
Hi,
On sam., 14 janv. 2023 at 23:07, Ludovic Courtès wrote:
> --8<---cut here---start->8---
> $ guix time-machine --commit=v1.2.0 -- size emacs
[...]
> total: 859.7 MiB
> $ guix time-machine --commit=v1.3.0 -- size emacs
[...]
> total: 880.5 MiB
> $ guix
Hi everyone,
I also don't see how Guix would gain anything from moving
to Guile's native exceptions. However, one thing that would be nice to
have is a description of all such "implementation choices" in Guix,
perhaps in the "Coding style" section of the manual. Having a
definitive reference to
Hi all,
On Tue, Jan 17, 2023 at 05:18 PM, Ludovic Courtès wrote:
> Hi,
>
> Efraim Flashner skribis:
>
>> I've made some progress on LLVM and I think I have a working LLVM that
>> can be used as an input for mesa.
>>
>> (ins)efraim@3900XT ~$ du -sch
>> /gnu/store/36kmnxmb1h8pxw0x71wril67fdvjx7ny
On Wed, 18 Jan 2023 at 00:05, zimoun wrote:
> For emacs-minimal, if considered to only bytecompile (.elc) and not
> native compile, this libgccgit seems unexpected, indeed. Well, is
> native compilation disabled for emacs-minimal? I guess not. :-)
The package emacs-minimal is only for byteco
Hi Julien,
On Wed, 11 Jan 2023 at 21:20, Julien Lepiller wrote:
> Sounds good to me. Are you planning to work on a patch?
Yes, I am planning to work on it. :-)
But maybe not in one go. Since it is a boring task, I plan to do
something similar as I did when “janitoring“ R packages from
biostat
Hi,
On Tue, 17 Jan 2023 at 17:25, Ludovic Courtès wrote:
> Examples include libgccjit in Emacs and mozjs in polkit.
Do I miss a point? How is it possible to have native compilation for
Emacs without libgccjit?
For emacs-minimal, if considered to only bytecompile (.elc) and not
native compile,
On 1/17/23 11:25, Ludovic Courtès wrote:
There are slight increases of each and every package, and there are also
new big dependencies being pulled in for what, from a distance, doesn’t
really add functionality.
Examples include libgccjit in Emacs and mozjs in polkit.
In a way, that’s the “una
28 matches
Mail list logo
