On Thu, Jul 21, 2016 at 07:53:45AM +0200, Ricardo Wurmus wrote:
Tomáš Čech writes:
First, I'm not saying that we should do that for every archive, but I
think that having a way how to automatically export this information
would be great and I see it as a week point for using Guix packages as
On Thu, Jul 21, 2016 at 1:33 AM, Ricardo Wurmus
wrote:
>
> Thompson, David writes:
>
>> On Wed, Jul 20, 2016 at 9:05 AM, Tomáš Čech wrote:
>>
>>> First, I'm not saying that we should do that for every archive, but I
>>> think that having a way how to automatically export this information
>>> wou
Andy Wingo skribis:
> On Tue 19 Jul 2016 00:22, l...@gnu.org (Ludovic Courtès) writes:
>
>> To recap, the difficulty with all this is that we couldn’t just call out
>> the ‘gzip’ command because ‘guix publish’ uses threads, and threads and
>> fork(2) don’t go together well.
>
> FWIW open-pipe or
On Tue 19 Jul 2016 00:22, l...@gnu.org (Ludovic Courtès) writes:
> To recap, the difficulty with all this is that we couldn’t just call out
> the ‘gzip’ command because ‘guix publish’ uses threads, and threads and
> fork(2) don’t go together well.
FWIW open-pipe or open-process from (ice-9 popen)
Tomáš Čech writes:
> First, I'm not saying that we should do that for every archive, but I
> think that having a way how to automatically export this information
> would be great and I see it as a week point for using Guix packages as
> alternative to Snappy or Flatpak.
Agreed. I think it’s un
Thompson, David writes:
> On Wed, Jul 20, 2016 at 9:05 AM, Tomáš Čech wrote:
>
>> First, I'm not saying that we should do that for every archive, but I
>> think that having a way how to automatically export this information
>> would be great and I see it as a week point for using Guix packages
On Wed, Jul 20, 2016 at 09:12:53AM -0400, Thompson, David wrote:
On Wed, Jul 20, 2016 at 9:05 AM, Tomáš Čech wrote:
First, I'm not saying that we should do that for every archive, but I
think that having a way how to automatically export this information
would be great and I see it as a week p
On Wed, Jul 20, 2016 at 9:05 AM, Tomáš Čech wrote:
> First, I'm not saying that we should do that for every archive, but I
> think that having a way how to automatically export this information
> would be great and I see it as a week point for using Guix packages as
> alternative to Snappy or Fla
On Wed, Jul 20, 2016 at 01:20:26PM +0200, Ricardo Wurmus wrote:
Tomáš Čech writes:
On Tue, Jul 19, 2016 at 04:23:14PM +0200, Ricardo Wurmus wrote:
Tomáš Čech writes:
Imagine situation where person A is running some distribution with
Guix package manager on top and has some set of his per
Tomáš Čech writes:
> On Tue, Jul 19, 2016 at 04:23:14PM +0200, Ricardo Wurmus wrote:
>>
>>Tomáš Čech writes:
>>
>>> Imagine situation where person A is running some distribution with
>>> Guix package manager on top and has some set of his personal packages
>>> containing additional patches whic
On Tue, Jul 19, 2016 at 04:23:14PM +0200, Ricardo Wurmus wrote:
Tomáš Čech writes:
Imagine situation where person A is running some distribution with
Guix package manager on top and has some set of his personal packages
containing additional patches which are not part of Guix GIT.
He'd like
Tomáš Čech writes:
> Imagine situation where person A is running some distribution with
> Guix package manager on top and has some set of his personal packages
> containing additional patches which are not part of Guix GIT.
>
> He'd like to share the package with person B, running different
> di
On Tue, Jul 19, 2016 at 03:15:38PM +0200, Ludovic Courtès wrote:
Hello Tomáš,
Tomáš Čech skribis:
As I am happy to see enthusiasm about Guix, I don't think that current
archive format is usable for distribution of binary packages of
whatever origin. Problem is that we have package definition
Hello Tomáš,
Tomáš Čech skribis:
> As I am happy to see enthusiasm about Guix, I don't think that current
> archive format is usable for distribution of binary packages of
> whatever origin. Problem is that we have package definition as part of
> package manager GIT snapshot or local files but t
On Tue, Jul 19, 2016 at 08:29:15AM +0200, Tomáš Čech wrote:
> I was thinking that we could (and should) add some optional support
> for metadata which could describe the origin of the package. It could
> contain:
> - Guix GIT revision used
> - differences against GIT revision
> - local package reci
On Tue, Jul 19, 2016 at 12:22:42AM +0200, Ludovic Courtès wrote:
Hi!
‘guix publish --compression’ can now compress archives in gzip format,
using zlib, which makes it much more usable in real life. See commit
4a1fc562ae5eedf40f6ae4eabe30580b0983b8f6.
‘guix publish’ is cache-friendly: it uses /
Hi!
‘guix publish --compression’ can now compress archives in gzip format,
using zlib, which makes it much more usable in real life. See commit
4a1fc562ae5eedf40f6ae4eabe30580b0983b8f6.
‘guix publish’ is cache-friendly: it uses /nar/gzip URLs for gzipped
archives, and /nar for uncompressed archi
17 matches
Mail list logo
