Re: Making local development easy

2016-06-21 Thread Ludovic Courtès
"Thompson, David" skribis: > On Thu, May 26, 2016 at 4:07 AM, Ludovic Courtès wrote: > >> Even shorter: >> >> (source "/some/file/out/there") >> >> or: >> >> (source ".") > > I think there is a bug here because I've tried this at various points > in time and it has never worked. A pattern m

Re: Making local development easy

2016-05-26 Thread Thompson, David
On Thu, May 26, 2016 at 4:07 AM, Ludovic Courtès wrote: > Even shorter: > > (source "/some/file/out/there") > > or: > > (source ".") I think there is a bug here because I've tried this at various points in time and it has never worked. A pattern matcher somewhere fails because a string isn'

Re: Making local development easy

2016-05-26 Thread Ludovic Courtès
Ricardo Wurmus skribis: > Christopher Baines writes: > >> On 25/05/16 11:29, Ricardo Wurmus wrote: >>> Christopher Baines writes: The second issue was getting the data to the store, as first I tried a relative path, but that did not work, and ended up having to expose the reposit

Re: Making local development easy

2016-05-25 Thread Ricardo Wurmus
Christopher Baines writes: > On 25/05/16 11:29, Ricardo Wurmus wrote: >> Christopher Baines writes: >>> The second issue was getting the data to the store, as first I tried a >>> relative path, but that did not work, and ended up having to expose the >>> repository using a HTTP server, and acce

Re: Making local development easy

2016-05-25 Thread Leo Famulari
On Wed, May 25, 2016 at 10:23:20AM +0200, Alex Sassmannshausen wrote: > Christopher Baines writes: > > The first, is that the hash is required, which I only had to compute > > once, but if I wanted to change the package, I would have to update > > this, which is prohibitive to local development. As

Re: Making local development easy

2016-05-25 Thread Christopher Baines
On 25/05/16 11:29, Ricardo Wurmus wrote: > Christopher Baines writes: >> The second issue was getting the data to the store, as first I tried a >> relative path, but that did not work, and ended up having to expose the >> repository using a HTTP server, and access it over the loopback >> interface

Re: Making local development easy

2016-05-25 Thread Christopher Baines
On 25/05/16 10:23, Alex Sassmannshausen wrote: >> The first, is that the hash is required, which I only had to compute >> once, but if I wanted to change the package, I would have to update >> this, which is prohibitive to local development. As an improvement to >> this, could the hash be optional,

Re: Making local development easy

2016-05-25 Thread Andy Wingo
On Tue 24 May 2016 20:25, Christopher Baines writes: > The first, is that the hash is required, which I only had to compute > once, but if I wanted to change the package, I would have to update > this, which is prohibitive to local development. As an improvement to > this, could the hash be optio

Re: Making local development easy

2016-05-25 Thread Alex Sassmannshausen
Ricardo Wurmus writes: > Christopher Baines writes: > >> The second issue was getting the data to the store, as first I tried a >> relative path, but that did not work, and ended up having to expose the >> repository using a HTTP server, and access it over the loopback >> interface. This again i

Re: Making local development easy

2016-05-25 Thread Ricardo Wurmus
Christopher Baines writes: > The second issue was getting the data to the store, as first I tried a > relative path, but that did not work, and ended up having to expose the > repository using a HTTP server, and access it over the loopback > interface. This again is rather prohibitive to local d

Re: Making local development easy

2016-05-25 Thread Alex Sassmannshausen
Hello, Christopher Baines writes: > Today I had a go at writing a dummy python library, and packaging it, > and then installing it within an environment, with the aim of > experimenting more with how Guix works, and to explore how Guix can be > used as a developer (with unpublished local packages

Making local development easy

2016-05-24 Thread Christopher Baines
Today I had a go at writing a dummy python library, and packaging it, and then installing it within an environment, with the aim of experimenting more with how Guix works, and to explore how Guix can be used as a developer (with unpublished local packages). There were several slight issues with th