On Sun, Mar 06, 2022 at 03:32:09PM +0100, Maxime Devos wrote:
> > + (define-public go-github-com-niemeyer-pretty
> > + (package
> > +(name "go-github-com-niemeyer-pretty")
> > +(version "0.0.0-20200227124842-a10e7caefd8e")
> > +(source
> > + (origin
> > +(method
Hello Philip,
Philip Kaludercic writes:
> reading [0], I would like to ask if there is any interest in
> up-streaming the work I have been doing to build old versions of Emacs
> using Guix (the main use-case is to help with testing Emacs packages on
> various versions)[1]?
This is a very
Hi,
On Monday, March 7, 2022 5:41:46 AM EST Ludovic Courtès wrote:
> Hi,
>
> Philip McGrath skribis:
> > To start with that, my proposed approach, which I hope satisfies the
> > FSDG, is here: https://github.com/racket/srfi/pull/15
>
> Good to know; I hope the next Racket release will include
On Mon, Mar 7, 2022 at 5:18 AM Ludovic Courtès wrote:
> The ‘clang’ definition reads:
>
> ;; Use a sane default include directory.
> (string-append "-DC_INCLUDE_DIRS="
> (assoc-ref %build-inputs "libc")
>
On Mon, 07 Mar 2022, Kaelyn wrote:
> On Sunday, March 6th, 2022 at 8:19 AM, Olivier Dion via "Development of GNU
> Guix and the GNU System distribution." wrote:
>
>> Hi Guix,
>>
>> I often find my self using inheritance of package to add native-inputs
>>
>> that are not stricly necessary for
Hello,
On Sunday, March 6th, 2022 at 8:19 AM, Olivier Dion via "Development of GNU
Guix and the GNU System distribution." wrote:
> Hi Guix,
>
> I often find my self using inheritance of package to add native-inputs
>
> that are not stricly necessary for building the project, but are used
>
>
Hi,
Philip McGrath skribis:
> To start with that, my proposed approach, which I hope satisfies the
> FSDG, is here: https://github.com/racket/srfi/pull/15
Good to know; I hope the next Racket release will include it.
Thank you,
Ludo’.
Hi Philip,
Philip McGrath skribis:
> Racket's state-of-the-art contract system has many features and nuances. I *do
> not* think anyone should try to implement them all in one fell swoop. I'm
> hoping there's a way to implement your simple assertions with only a modest
> amount of overhead that
Hi,
Greg Hogan skribis:
> I'd like to instead use the latest gcc-toolchain (currently gcc-toolchain@11)
> and have clang-toolchain built with that gcc-toolchain. No matter what
> I offer in the "--with-c-toolchain" or "--with-input" options I always see
> the following error regarding
