On Fri Dec 9, 2022 at 7:31 AM GMT, 宋文武 wrote:
> I think it's missing what "build-derivations" do, or "Part 0: Store".
Hmm, do you mean adding an example of building a derivation in Scheme with
``build-derivations''? I'll definitiely add that :)
-- (
signature.asc
Description: PGP
"(" writes:
> Heya!
>
> Some of you may have seen on IRC that I've been writing a post for the Guix
> blog that I hope will form the first part of a series. This series aims to
> dissect the internals of Guix, from bottom to top. Perhaps they could go in
> the cookbook once the series is done?
Hi,
On Sun, 04 Dec 2022 at 11:35, indieterminacy
wrote:
> Given Fosshost's place in the ecosystem: is this something which
> requires mitigating at the Guix end?
On Sun, 04 Dec 2022 at 13:16, Tobias Geerinckx-Rice wrote:
> - They hosted a Big Blue Button instance[0] only for the duration
Hi,
On Tue, 06 Dec 2022 at 10:38, pinoaffe wrote:
> I don't know why this file is renamed,
The explanations are here: :-)
https://issues.guix.gnu.org/51755#5
or here: :-)
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/coq.scm#n217
> Does anyone know what's going on,
Hi Guix!
I had a look at gcc to try and reduce its footprint. I figured gcc-lib
contained shared and static libraries as well as support libraries for
gdb, many headers and compiler runtime, that are taking a lot of space
when they are not needed at runtime. Reducing its 33.4 MiB would help
Heya!
Some of you may have seen on IRC that I've been writing a post for the Guix
blog that I hope will form the first part of a series. This series aims to
dissect the internals of Guix, from bottom to top. Perhaps they could go in
the cookbook once the series is done? My aim is to write the
Hello Guix!
Release progress: week 9.
Here are the main improvements that landed on ‘version-1.4.0’ since RC1:
• System test failures and ARM image build failures fixed:
https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00063.html
• Missing file added to Makefile.am:
Heya,
On Wed Dec 7, 2022 at 11:09 PM GMT, Christopher Howard wrote:
> This almost works, but the build fails because of a path issue:
>
> ```
> starting phase `build'
> src/golang.org/x/net/idna/idna10.0.0.go:25:2: cannot find package
> "golang.org/x/text/secure/bidirule" in any of:
>
>
Hi folks,
the proof-general package seems to be broken - I cannot load it from
emacs, even when it is properly installed and in the path. I've tried
requiring proof-general, proof-general-autoloads, and loading it using
use-package. I think the issue is that proof-general.el is renamed to
Hello, I was trying to package some go software, using a definition based on
what I got from the importer. This is my working definition:
```
(define-public go-git-sr-ht-adnano-go-gemini
(package
(name "go-git-sr-ht-adnano-go-gemini")
(version "0.2.3")
(source (origin
Jonathan Brielmaier skribis:
> On 03.12.22 23:45, Vagrant Cascadian wrote:
>> On 2022-12-01, Ludovic Courtès wrote:
>>> I’m pleased to announce Guile-Gcrypt version 0.4.0:
>>>
>>>git clone https://notabug.org/cwebber/guile-gcrypt.git
>>>cd guile-gcrypt
>>>git checkout v0.4.0 # or
Hi,
zamfofex skribis:
> configure:10478: checking C++ compiler i586-pc-gnu-g++ -m32 -O2 -pedantic
> -fomit-frame-pointer
> Test compile:
> configure:10492: i586-pc-gnu-g++ -m32 -O2 -pedantic -fomit-frame-pointer
> conftest.cc >&5
> i586-pc-gnu-ld:
>
Hi,
"(" skribis:
> Someone on IRC suggested that we use GraphQL to allow us to request
> that a substitute server search for files in a database constructed
> using all the packages that have been built.
>
> I suggest something like this:
>
> # on the client
> when [built a package
Denis 'GNUtoo' Carikli writes:
> [[PGP Signed Part:Undecided]]
> Hi,
>
> Is there any policies or past decisions of the Guix project on
> packaging big generated data files?
>
> I've added packages for software like kiwix-tools and navit that both
> work offline but that also need data files
Hi,
On Wed, 07 Dec 2022 at 17:22, jgart wrote:
> What is our policy then for updating Python packages in our Python
> library collection?
The policy is to not break the other packages; guix refresh -l python-.
> How are we assuring that all Python libraries are working well together?
How?
Tobias Geerinckx-Rice writes:
> indieterminacy 写道：
>> Given Fosshost's place in the ecosystem: is this something which
>> requires mitigating at the Guix end?
>
> I'm aware of two dealings with Fosshost in the past, neither of them
> crucial:
> - They hosted a Big Blue Button instance[0] only
16 matches
Mail list logo
