Re: Go importer and packages with version flags

Katherine Cox-Buday writes: > Sarah Morgensen writes: > >> Hi Katherine, Jack, >> >> Katherine Cox-Buday writes: >> >>> Jack Hill writes: >>> >>>> Hi Guix, >>> >>> Hey, Jack, a few thoughts. >>> >>>

Re: Go importer and packages with version flags

Hi Katherine, Jack, Katherine Cox-Buday writes: > Jack Hill writes: > >> Hi Guix, > > Hey, Jack, a few thoughts. > >> While I was was working with the go importer today, it suggested I package >> go-github-com-russross-blackfriday-v2. Fair enough, except we already have a >> package for

Re: Named environments

Ryan Prior writes: > Hey Guix. > > I've been thinking lately it would be convenient to create certain uniquely > named execution environments on my machine. For example, I might have one > set up with dependencies for my Python webapp & environment variables set to > autoconnect to a Postgres

Re: Batching world-rebuilding changes for the core-updates-frozen branch

Hi, Maxim Cournoyer writes: > Hello Guix! > > Since there's going to be at least this change [0] causing a world > rebuild of the core-updates-frozen branch, I'd like to know if there are > other world-rebuilding but low-risk changes you'd like to see integrated > into the branch. Perhaps we

Re: gcc: build all languages at once?

Hi Ludo, Ludovic Courtès writes: > Hi Sarah, > > Sarah Morgensen skribis: > >> I notice that out of GCC's supported languages (ada, c, c++, d, fortran, >> go, jit, lto, objc, obj-c++) we currently build all except ada, and five >> of them (d, fortran, go

Re: Rethinking propagated inputs?

e current problems with it, and what would the advantages be > to move away from the status quo? If there aren't clear benefits, I'd > prefer the status quo, abstaining from the added complexity. As I mentioned up-thread: Sarah Morgensen writes: >> Does anyone have an idea how we should ha

Re: Rethinking propagated inputs?

Hi Liliana, (Efraim, I've Cc'd you since you're working on re-doing Rust inputs.) Liliana Marie Prikler writes: > Does anyone have an idea how we should handle propagations for the sake > of pkg-config? Perhaps we could add "linked-inputs", which are added > when building packages and

Re: Can we find a better idiom for unversioned packages?

Liliana, Thanks for the criticism! Liliana Marie Prikler writes: > Hi > > Am Dienstag, den 31.08.2021, 23:20 +0200 schrieb Maxime Devos: >> Sarah Morgensen schreef op di 31-08-2021 om 12:57 [-0700]: >> > Hello Guix, >> > >> > Currently,

Re: Can we find a better idiom for unversioned packages?

Hi Maxime, Maxime Devos writes: >> > Not losing the revision is useful for things like >> > ;, to be able to determine the old >> > revision. (That's not about inheriting packages though.) > >> Isn't that addressed by addressing the second point, though?

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

Hi, Maxime Devos writes: >> > have uses outside go-ethereum, so they can be re-used as dependencies of >> > new go packages, so over time, having to define many new packages when >> > importing >> > a go application should become less and less of a problem. >> > >> > (About version pinning:

Can we find a better idiom for unversioned packages?

Hello Guix, Currently, there are about 1500 packages defined like this: --8<---cut here---start->8--- (define-public sbcl-feeder (let ((commit "b05f517d7729564575cc809e086c262646a94d34") (revision "1")) (package [...])))

gcc: build all languages at once?

Hello Guix, I notice that out of GCC's supported languages (ada, c, c++, d, fortran, go, jit, lto, objc, obj-c++) we currently build all except ada, and five of them (d, fortran, go, objc, and obj-c++) are built separately. Most of GCC's build time is spent bootstrapping and building the actual

Re: Hundreds of failed build on master following git package update

Hello, br...@waegenei.re writes: > Hello Guix, > > Today I pushed 2 commits¹ related to the package to master, mainly to update > it to 2.33.0. But since then https://data.guix.gnu.org/ went offline and > Cuirass' evaluation #4930² has 556 failed build. Newly failed builds have > unhelpful

Re: Mailman From header rewrite

Hello Ryan, others, I too recently noticed that my From header is getting rewritten! My domain is set up with DKIM, SPF, and DMARC, so I suppose this is not surprising. Before sending this mail, I attempted two fixes: 1. add '?include:lists.gnu.org' to my SPF record; and 2. set 'p=none;' in