On Wed, 20 Sep 2017 08:20:18 +0200
Jan Nieuwenhuizen wrote:
> Christopher Baines writes:
>
> > Providing these packages sit within the Guix repository,
>
> ...and if they don't you can set
>
> (#:load-path . "/your/packages/directory")
>
> (It says path, but means directory I think).
>
Christopher Baines writes:
> Providing these packages sit within the Guix repository,
...and if they don't you can set
(#:load-path . "/your/packages/directory")
(It says path, but means directory I think).
> I think there are configuration examples for building a subset of
> packages alre
On Tue, 19 Sep 2017 11:24:45 +0300
Efraim Flashner wrote:
> On Mon, Sep 18, 2017 at 09:59:06PM +0100, Christopher Baines wrote:
> > Hey,
> >
> > At the GHM, one of the things I looked in to was cuirass.
> > Specifically, I tried to see if I could build a collection of guix
> > packages that sit
Christopher Baines transcribed 3.8K bytes:
> Hey,
>
> At the GHM, one of the things I looked in to was cuirass. Specifically,
> I tried to see if I could build a collection of guix packages that sit
> outside of Guix.
I would be very much interested in exploring the possibility
(at the very least
On Mon, Sep 18, 2017 at 09:59:06PM +0100, Christopher Baines wrote:
> Hey,
>
> At the GHM, one of the things I looked in to was cuirass. Specifically,
> I tried to see if I could build a collection of guix packages that sit
> outside of Guix.
>
...
>
> Does anyone have any opinions or ideas about
Hey,
At the GHM, one of the things I looked in to was cuirass. Specifically,
I tried to see if I could build a collection of guix packages that sit
outside of Guix.
From trying to use cuirass for a few hours, I began thinking that it
might be beneficial to change the interface between cuirass and
