On Mon, Jun 07, 2021 at 08:48:11PM +0200, Leo Prikler wrote:
> (Note, though, that a Go update would need to go through staging – not
> an ideal situation either.)
I have "cheated" regarding this in the past. Although changing the Go
package should qualify for staging, it's so cheap to build Go
On Tue, Mar 23 2021, zimoun wrote:
>> Maybe its time to update to a newer Stackage LTS release? :)
>
> Well, I do not know if it possible to do so before the next release.
> IMHO, let focus on what remains for the next release and let upgrade the
> Stackage LTS after.
Any updates on this? I
On Mon, Jun 07, 2021 at 06:41:41PM +0200, Hartmut Goebel wrote:
> Am 07.06.21 um 18:26 schrieb Hartmut Goebel:
> > > Another path we should checkout is to see what Debian does. My
> > > understanding is that they figured something out. Worth a shot, but
> > > I’d rather the problem be fixed
Hi!
Mathieu Othacehe skribis:
> Cuirass is now able to generate badges like any respectable CI
> system. For instance:
>
> * https://ci.guix.gnu.org/jobset/master/badge generates a badge showing
> the percentage of successful jobs for the master specification.
Fanciness. :-)
This is not
Hello!
Efraim Flashner skribis:
> Porting Guix comes with two parts: building the bootstrap-tarballs and
> adding support for the new architecture in (gnu packages bootstrap).
> Support for riscv was added to GCC with 7.1.0 so I had to bump the
> bootstrap GCC to 7 (and adjust some inputs), and
Hi!
(I’m late to the party…)
Pjotr Prins skribis:
> As Guix takes care of the first and the last - the issue centers
> around building. The idea is to dress down these language specific
> builders, such as cargo, so you don't have all the included
> complexity.
>
> A sexp-pack would represent
Hi Paul,
"Paul A. Patience" skribis:
> What is the standard place to put documentation?
> The license files are automatically installed to the
> share/doc/NAME-VERSION directory
> (see install-licence-files in gnu-build-system.scm),
> but it seems like various packages install the actual
>
Hi,
Christopher Baines skribis:
> I think things are pretty much ready, you can find some information at
> https://bordeaux.guix.gnu.org/ . If you're up for trying out fetching
> substitutes from bordeaux.guix.gnu.org, now is a good time to do so, and
> please report back in terms of how it's
Hi,
Ricardo Wurmus skribis:
> Ludovic Courtès writes:
>
>> Hi!
>>
>> Ricardo Wurmus skribis:
>>
>>> There are two problems here:
>>>
>>> 1) I don’t think “guix gc --list-dead” (or “--list-live”, or more
>>> generally “findRoots” in nix/libstore/gc.cc) should delete
>>> anything. It should
Hi,
Ryan Prior skribis:
> I think there's an opportunity to avoid the need to "fall back" to the status
> quo, though. I picture a structure for inputs that has three cases, trivially
> decided based on data shape:
>
> - a bare symbol, eg '(tzdata glib)
> this is translated to `(("tzdata"
Hi,
Raghav Gururajan skribis:
> Quite a few people I know, who tried guix for first time on foreign
> distro, mentioned to me that they presumed the installation script to
> cover everything, including application-setup.
>
> Is it possible to automate application-setup through the installation
Am 08.06.21 um 11:15 schrieb Efraim Flashner (referring to Debian)
My understanding is that they pool together all the sources that they
have and then build all the rust packages in one go.
Maybe, I have no clue. Anyhow given my experience with sequoia, I doubt
this will reduce build-times:
Hi Ludovic,
On Tuesday, June 8th, 2021 at 09:31, Ludovic Courtès wrote:
> Right, share/doc/NAME appears to be more common (perhaps we should fix
> ‘install-licence-files’).
I suppose the advantage of having the version name in the path is
allowing several versions of a library to be installed
13 matches
Mail list logo
