Re: Packages grow, no longer fit on a 💾

Paul Jewell via "Development of GNU Guix and the GNU System distribution." writes: > Evening all, > > On 14/01/2023 23:07, 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--

Re: FOSDEM’s coming!

Hi Ludo’, On Thu, Jan 19, 2023 at 04:58 PM, Ludovic Courtès wrote: > Hello Guix! > > I’ve prepared a blog post about FOSDEM and the Guix Days that we could > publish tomorrow (Friday) or Monday: > > >

Re: FOSDEM’s coming!

Hi Ludo, > Please take a look and send patches if needed! If someone can come up > with some kind of a logo for the Guix Days, that’d be great; otherwise > we’ll just reuse the one from last year. note that the Guix Days take place on February *2nd and 3rd* (correctly identified as Thursday and F

Re: Grandfathering store paths considered harmful

Am Donnerstag, dem 19.01.2023 um 15:28 +0100 schrieb Ludovic Courtès: > Hi Liliana, > > Liliana Marie Prikler skribis: > > > For context, emacs uses a hash digest to more or less uniquely > > fingerprint the version (much like guix does), so natively > > compiling things with emacs-minimal won't

Re: Packages grow, no longer fit on a 💾

Ludovic Courtès writes: > Even from a purely practical perspective, it’s not convenient when > ‘guix pack’ creates big images that you have to carry around and your > colleague laughs at you because their Alpine image of “the same thing” > (quotes!) is half the size. ;-) I know this pain! -- K

Re: Exception: srfi-35 vs (ice-9 exceptions (was Re: [bug#60802] [PATCH v2 1/2] platforms: Raise an exception when no suitable platform is found.)

Ludovic Courtès writes: > Hi, > > Josselin Poiret skribis: > >> 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 sty

FOSDEM’s coming!

Hello Guix! I’ve prepared a blog post about FOSDEM and the Guix Days that we could publish tomorrow (Friday) or Monday: https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/drafts/meet-guix-at-fosdem-2023.md Please take a look and send patches if needed! If someone can come u

Re: Packages grow, no longer fit on a 💾

John Kehayias writes: >>> 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. This is awesome! Thank you Efraim! > I don't think there were any errors in building mesa with older LLVM, > but on current ha

Re: Exception: srfi-35 vs (ice-9 exceptions (was Re: [bug#60802] [PATCH v2 1/2] platforms: Raise an exception when no suitable platform is found.)

Hi, Josselin Poiret skribis: > 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

Re: Packages grow, no longer fit on a 💾

Hi, Paul Jewell via "Development of GNU Guix and the GNU System distribution." skribis: > - Can an ISO be bigger than a CD then be installed on a memory stick? Yes, it can be installed from a memory stick, that’s probably what everybody does. > It strikes me that this is like King Canute holdi

Re: Packages grow, no longer fit on a 💾

Simon Tournier skribis: > Just to note to Guix itself significantly grows. :-) Yes! There’s a lot of .scm and .go files in there, neither of which is compact. Ludo’.

Re: Packages grow, no longer fit on a 💾

Hi, kiasoc5 skribis: > We may wish to utilize multiple package outputs to a greater > extent. Some Guix packages already have bin, doc, and lib outputs. We > could make it a policy to split this for all packages. There’s some a policy already, though maybe not universally followed; see point 8

Re: Grandfathering store paths considered harmful

Hi Liliana, Liliana Marie Prikler skribis: > For context, emacs uses a hash digest to more or less uniquely > fingerprint the version (much like guix does), so natively compiling > things with emacs-minimal won't speed up your packages when using emacs > or emacs-next and is thus next to pointle

Re: Packages grow, no longer fit on a 💾

Hi, zimoun skribis: > 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? I wrote: > there are also new big dependencies being pu

Re: Packages grow, no longer fit on a 💾

Paul Jewell via "Development of GNU Guix and the GNU System distribution." writes: > Evening all, > > > Please forgive my ignorance if I have missed anything but: > > - does anyone actually install from a CD these days? > - Can an ISO be bigger than a CD then be installed on a memory stick? > > I

Re: #:configure-flags flags #~'() or #:configure-flags flags #~()

In this example, only #~'() makes sense. #~() is nonsensical here and will cause a syntax error when ungexped. Kind regards, T G-R Sent on the go. Excuse or enjoy my brevity.

Re: #:configure-flags flags #~'() or #:configure-flags flags #~()

Tobias Geerinckx-Rice writes: > Hi! > > It's not about 'right' (why would grepping Guix return wrong code...? > Impossible! :-). It's a matter partly of preference and partly of using the > best tool for the job. > > Omitted from your second example is a call to list, and the #~ that both have

Re: IDEA: Give Our Generations a Name

Liliana Marie Prikler writes: > Am Dienstag, dem 17.01.2023 um 01:52 + schrieb Csepp: >> >> "jgart" writes: >> >> > Hi Guixers, >> > >> > What do you think if we would be able to give past generations a >> > name? >> > >> > I'm thinking of the way you can do the following with git: >>

Re: #:configure-flags flags #~'() or #:configure-flags flags #~()

Hi! It's not about 'right' (why would grepping Guix return wrong code...? Impossible! :-). It's a matter partly of preference and partly of using the best tool for the job. Omitted from your second example is a call to list, and the #~ that both have in common is just syntactic sugar for (gex