Thompson, David writes:
> Ricardo, you are correct that we would lose the ability to use the
> guix.scm file for both 'guix environment' and 'guix build'. In
> practice I don't actually use my guix.scm file this way, so I think
> it's worth breaking, but maybe you (or someone else) actually uses
Not going to reply in detail, but I'm a devoted user of `guix
environment' and I support all these changes!
On Thu, Aug 31, 2017 at 11:16 AM, Ludovic Courtès wrote:
> Heya,
>
> "Thompson, David" skribis:
>
>> If you've followed along this far, great! Now here's my list of
>> proposed changes:
>>
>> 1) Add a caching mechanism. The environment profile should get
Leo Famulari writes:
> On Thu, Aug 31, 2017 at 09:52:49PM +0200, Marius Bakke wrote:
>> Side note: I think we should start adding patches as origins instead of
>> copying them wholesale, to try and keep the git repository slim.
>
> We should make a git-minimal package for
On Thu, Aug 31, 2017 at 09:52:49PM +0200, Marius Bakke wrote:
> Side note: I think we should start adding patches as origins instead of
> copying them wholesale, to try and keep the git repository slim.
We should make a git-minimal package for things like this, or use
guile-git / libgit2. Git
On Tue, Aug 29, 2017 at 03:54:40PM +0300, Frederick Muriithi wrote:
> Maybe the following will help clarify the issue:
>
> The package being built needs the sources of the dependenc(y/ies) to
> be available in its GOPATH.
>
> The build system needs to set the GOPATH such that the Go build system
Marius Bakke writes:
> Ludovic Courtès writes:
>
>> Marius Bakke skribis:
>>
>>> Efraim Flashner writes:
>>>
On Wed, Aug 30, 2017 at 09:10:42PM +0200, Marius Bakke wrote:
> Since we're on the topic, I
Ludovic Courtès writes:
> Marius Bakke skribis:
>
>> Efraim Flashner writes:
>>
>>> On Wed, Aug 30, 2017 at 09:10:42PM +0200, Marius Bakke wrote:
Since we're on the topic, I would like to switch to GCC 6 or 7 soon...
Are we
Heya,
"Thompson, David" skribis:
> If you've followed along this far, great! Now here's my list of
> proposed changes:
>
> 1) Add a caching mechanism. The environment profile should get built
> once, and then a symlink to it should be created in $PWD and
> registered
Hello!
Ricardo Wurmus skribis:
> @Dave: I pretty much agree with all of the proposed changes. One thing
> that may be lost, though, when using a new record is
> easy ad-hoc packaging.
>
> Now I can use a guix.scm file both for building a Guix package and a
> Docker image;
Heya,
Andreas Enge skribis:
> I have a probably naïve question, since I did not follow the project closely:
> Instead of an all-or-nothing outcome, success or failure, merge or bit rot,
> would it be possible to set up an incremental update path?
> Use some of your scheme code
Marius Bakke skribis:
> Efraim Flashner writes:
>
>> On Wed, Aug 30, 2017 at 09:10:42PM +0200, Marius Bakke wrote:
>>> Since we're on the topic, I would like to switch to GCC 6 or 7 soon...
>>> Are we agile enough to use the very latest GCC by default
On Thu, Aug 31, 2017 at 3:18 AM, Jan Nieuwenhuizen wrote:
> Thompson, David writes:
>
>> Hi all, been awhile!
>
> Hi David!
>
> Great suggestions all! I use guix environment heavily and like it a
> lot.
Thanks!
>> 4) Make 'guix environment' with no other args operate like
Thompson, David writes:
> Hi all, been awhile!
Hi David!
Great suggestions all! I use guix environment heavily and like it a
lot.
> 4) Make 'guix environment' with no other args operate like 'guix
> environment --cache --load=guix.scm'. 'guix.scm' is a placeholder
> name for whatever we
14 matches
Mail list logo