Re: wrap-program

2014-10-02 Thread Andreas Enge
Hello, I am only now catching up with the discussion. So far, I do not understand why we need a wrapper. Would it not be enough to add the environment variables $XDG_DATA_DIRS etc. to the search paths of the programs, in the same way as perl or python modules incite the user to define the correspo

Re: [PATCH 3/3] gnu: Add ruby-i18n.

2014-10-02 Thread Ludovic Courtès
"Thompson, David" skribis: > On Wed, Oct 1, 2014 at 3:28 PM, Ludovic Courtès wrote: >> Hello, >> >> I just noticed this: >> >> $ guix gc --references >> /gnu/store/whj6j9f34adpzwhfj3qf00fcq9zsb3hp-ruby-i18n-0.6.11 >> [nothing here] >> >> Apparently the .gem is +/- a gzip archive, which make

Re: wrap-program

2014-10-02 Thread Ludovic Courtès
Andreas Enge skribis: > I am only now catching up with the discussion. So far, I do not understand > why we need a wrapper. Would it not be enough to add the environment variables > $XDG_DATA_DIRS etc. to the search paths of the programs, in the same way as > perl or python modules incite the use

Re: [PATCH] gnu: Add dfu-programmer

2014-10-02 Thread Ludovic Courtès
Manolis Ragkousis skribis: > On 29 September 2014 19:09, Ludovic Courtès wrote: [...] >> I think the bug is rather that pkg-config is missing, because libusb.pc >> has this line: >> >> Cflags: -I${includedir}/libusb-1.0 >> >> Could you try adding it as a native input and report back? > > I d

Bags

2014-10-02 Thread Ludovic Courtès
Hello, I’ve pushed a new branch, ‘wip-bags’, which changes the way build systems work. Basically, it introduces an intermediate representation between packages and derivations, called “bags.” The main difference between a bag and a package is that a bag lists all the inputs of the build process,

Re: Bags

2014-10-02 Thread Thompson, David
On Thu, Oct 2, 2014 at 8:33 AM, Ludovic Courtès wrote: > Hello, > > I’ve pushed a new branch, ‘wip-bags’, which changes the way > build systems work. Basically, it introduces an intermediate > representation between packages and derivations, called “bags.” > > The main difference between a bag an

[PATCH] emacs: Add support for modifying options during operation confirmation.

2014-10-02 Thread Alex Kost
Hello, This is a little improvement for Emacs UI. I often found myself modifying ‘guix-dry-run’ variable during experiments with Guix. So I thought it would be more convenient to see the current state of "substitutes" or "dry-run" options and to change them on the fly, i.e. when you are prompted

Re: [PATCH] emacs: Add support for modifying options during operation confirmation.

2014-10-02 Thread Ludovic Courtès
Alex Kost skribis: > I often found myself modifying ‘guix-dry-run’ variable during > experiments with Guix. So I thought it would be more convenient to see > the current state of "substitutes" or "dry-run" options and to change > them on the fly, i.e. when you are prompted for confirmation of th

Re: Bags

2014-10-02 Thread Mathieu Lirzin
l...@gnu.org (Ludovic Courtès) writes: > The main difference between a bag and a package is that a bag lists all > the inputs of the build process, including the “implicit inputs” added > by the build system. Can you explain what you mean by "implicit inputs"?

Re: Bags

2014-10-02 Thread Thompson, David
On Thu, Oct 2, 2014 at 4:14 PM, Mathieu Lirzin wrote: > > l...@gnu.org (Ludovic Courtès) writes: >> The main difference between a bag and a package is that a bag lists all >> the inputs of the build process, including the “implicit inputs” added >> by the build system. > > Can you explain what you