Re: 02/02: linux-libre: Enable module compression.

Hello, >> * gnu/packages/aux-files/linux-libre/5.8-arm.conf: Enable GZ compression. >> * gnu/packages/aux-files/linux-libre/5.8-arm64.conf: Ditto. >> * gnu/packages/aux-files/linux-libre/5.8-i686.conf: Ditto. >> * gnu/packages/aux-files/linux-libre/5.8-x86_64.conf: Ditto. > > Sho

Re: File search progress: database review and question on triggers

Hi Pierre, Cool to relive the topic. :-) (disclaim: I have not yet process all the thread and emails) On Mon, 10 Aug 2020 at 16:32, Pierre Neidhardt wrote: > 1. An SQLite database with the following schema: If you are going to an local SQL database, my two questions are: a) Which part would

Re: Guix containers 'advertised' in git repos

Hi Pjotr, On Mon, 10 Aug 2020 at 12:36, Pjotr Prins wrote: > We are using Guix containers for deployment and software development. > I was thinking it would be nice to advertise them in the git repos. > > Maybe we can standardise on that. What I have now is have a file > > .git-deploy > > for d

Re: File search progress: database review and question on triggers

Hi Simon! zimoun writes: > If you are going to an local SQL database, my two questions are: > > a) > Which part would update it? “guix pull”? Other? Even using > substitutes, the channels and co could lead to an extra cost and so what > is acceptable and what is not? I suggest fetching datab

Re: File search progress: database review and question on triggers

Hi Pierre, On Thu, 27 Aug 2020 at 13:15, Pierre Neidhardt wrote: > zimoun writes: > >> If you are going to an local SQL database, my two questions are: >> >> a) >> Which part would update it? “guix pull”? Other? Even using >> substitutes, the channels and co could lead to an extra cost and s

Re: File search progress: database review and question on triggers

zimoun writes: > I am not sure to see how. One needs all the database to search inside > and cannot know in advance which packages etc.. Contrary to “guix size” > which manipulates the graph and then download the missing parts. > > Therefore, your suggestion is to download all the database the

[PATCH v4] gnu: emacs: Update to 27.1.

From: Morgan Smith * gnu/packages/emacs.scm (emacs): Update to 27.1. [arguments]: Add --with-cairo and --with-modules to #:configure-flags. Add restore-emacs-pdump phase. [inputs]: Add cairo, libxaw, jansson, gmp, and harfbuzz. Remove imagemagick and libxft. [native-inputs]: Add texlive. (emacs-w

[PATCH] hydra: Use the new 'systems' field for build-machine definitions.

* hydra/machines-bayfront.scm (harbourfront): Change system to systems, and include i686-linux in the list of systems. (milano): Likewise. (harbourfront-i686): Remove. (milano-i686): Likewise. (dover, redhill): Adapt to use the new systems field. * hydra/machines-for-berlin.scm (template-x86_64): C

Re: Setuid programs

Hello Gabor! Gábor Boskovits writes: > Hello guix, > > I would like to propose an extension to how setuid programs are > currently handled. The last time I checked it could only do setuid and > setgid root. Some services, such as postfix need a more fine grained > setuid setup. I would propose a

Re: [bug#42738] [PATCH v4] gnu: emacs: Update to 27.1.

Hi Morgan, On Thu, 27 Aug 2020, morgan.j.sm...@outlook.com wrote: From: Morgan Smith * gnu/packages/emacs.scm (emacs): Update to 27.1. [arguments]: Add --with-cairo and --with-modules to #:configure-flags. Add restore-emacs-pdump phase. [inputs]: Add cairo, libxaw, jansson, gmp, and harfbuzz.

Re: [PATCH] hydra: Use the new 'systems' field for build-machine definitions.

Hello Maxim, > (fast/hurd (filter (compose childhurd-ip? build-machine-name) fast))) >(append overdrive (map aarch64->armhf overdrive) > armv7 > - x86_64 (map x86_64->i686 x86_64) > + x86_64 > (map x86_64->qemu-aarch64 fast) > (map x86_64->qemu-arm