Hello!
I’ve been doing some polishing (and adding a few packages), but I think
I’ll tag the new version tomorrow (Sunday 12th).
Ludo’.
We’re getting there! I propose releasing sometime between May 7th and
May 12th.
There’s room for improvement to the manual and website, please share
your ideas and patches!
Ludo’.
l...@gnu.org (Ludovic Courtès) skribis:
> I think we should plan for 0.2 within a month or so. Here are the
> important features I’d like to see in:
>
> • ‘guix pull’ (see TODO; I’ve started working on that);
>
> • a simple “binary substituter”, which would allow pre-built binaries
> to b
> I wouldn’t bother, though, because it will be used in contexts where
> there’s no risk of ‘prog’ being used while we’re fiddling with it
> (single-threaded, after ‘make install’).
Better safe than sorry. So I added '.PROG-tmp'.
> Can you just expound the docstring before pushing?
Is it OK? C
Nikita Karetnikov skribis:
> Is there a way to compose the following part somehow to prevent a
> possible race condition?
>
> (rename-file prog prog-real)
>
> (with-output-to-file prog (lambda ()
> (format #t
> "#!~a~
What about this patch?
Is there a way to compose the following part somehow to prevent a
possible race condition?
(rename-file prog prog-real)
(with-output-to-file prog (lambda ()
(format #t
"#!~a~%~a~%exec ~a~%"
Nikita Karetnikov skribis:
>> It’s not needed. All that needed is the name of the executable file
>> to wrap.
>
> I don't understand. How will 'rename-file' get the location of the
> executable? For example:
>
> (wrap-program "wget" [...])
>
> I guess that it will only work if you invoke 'wrap
> It’s not needed. All that needed is the name of the executable file
> to wrap.
I don't understand. How will 'rename-file' get the location of the
executable? For example:
(wrap-program "wget" [...])
I guess that it will only work if you invoke 'wrap-program' from the
same directory.
> For
Nikita Karetnikov skribis:
>> Remember that (guix build ...) modules must not use Guix modules other
>> than (guix build ...). This is a convention to distinguish between code
>> for the “builder stratum”, and code for the “host stratum”.
>
> OK. But how can I get the location of a package? Th
> Remember that (guix build ...) modules must not use Guix modules other
> than (guix build ...). This is a convention to distinguish between code
> for the “builder stratum”, and code for the “host stratum”.
OK. But how can I get the location of a package? The needed procedure
(i.e., 'package-
Nikita Karetnikov skribis:
> ice-9/boot-9.scm:106:20: In procedure # ice-9/boot-9.scm:97:6 (thrown-k . args)>:
> ice-9/boot-9.scm:106:20: In procedure module-lookup: Unbound variable: memoize
As Mark noted, that’s because of a circular dependency.
> (define-module (wrap-program)
> #:use-modul
Nikita Karetnikov writes:
> I'm attaching a patch.
>
> It's a separate file; if I add these lines
>
>#:use-module (guix packages)
>#:use-module (guix store)
>
> to 'guix/build/utils.scm', they will raise the following error on
> 'make'.
Based on the backtrace below, it looks like you tri
I'm attaching a patch.
It's a separate file; if I add these lines
#:use-module (guix packages)
#:use-module (guix store)
to 'guix/build/utils.scm', they will raise the following error on
'make'.
Backtrace:
In ice-9/eval.scm:
400: 19 [eval # ()]
In ice-9/boot-9.scm:
2681: 18 [define-modul
Nikita Karetnikov skribis:
>> With the recently-added ‘package-output’ (singular):
>
>> scheme@(guile-user)> (package-output s binutils "out")
>> $2 = "/nix/store/bfh5c2a4is27jdmc811fp6g0jfac7fiw-binutils-2.22"
>> scheme@(guile-user)> (package-output s binutils "lib")
>> $3 = "/nix/store/n29brzql
> With the recently-added ‘package-output’ (singular):
> scheme@(guile-user)> (package-output s binutils "out")
> $2 = "/nix/store/bfh5c2a4is27jdmc811fp6g0jfac7fiw-binutils-2.22"
> scheme@(guile-user)> (package-output s binutils "lib")
> $3 = "/nix/store/n29brzqlhjkzww51labk9anx493gl4d3-binutils-2
Nikita Karetnikov skribis:
>> wrapProgram $out/bin/guile-snarf --prefix PATH : "${gawk}/bin"
>
> How can I get the output of a package?
With the recently-added ‘package-output’ (singular):
--8<---cut here---start->8---
scheme@(guile-user)> (package-output s
Am Sonntag, 17. Februar 2013 schrieb Ludovic Courtès:
> • Xorg & co. packaged (Andreas? :-));
Ok, I will have a look during the weekend.
Andreas
> wrapProgram $out/bin/guile-snarf --prefix PATH : "${gawk}/bin"
How can I get the output of a package? There is 'package-outputs':
scheme@(guile-user)> ,use (gnu packages wget) (guix packages)
scheme@(guile-user)> (package-outputs wget)
$1 = ("out")
But how can I get the value (like in '#:pha
Nikita Karetnikov skribis:
> I guess that I can implement this one:
>
> ** Add equivalent to Nixpkgs's ‘wrapProgram’
>
> What's the purpose of 'wrapProgram'? Could you elaborate?
Here’s an example from the Guile expression in Nixpkgs:
wrapProgram $out/bin/guile-snarf --prefix PATH : "${gawk}
I guess that I can implement this one:
** Add equivalent to Nixpkgs's ‘wrapProgram’
What's the purpose of 'wrapProgram'? Could you elaborate?
pgpPSf2Ka2i9D.pgp
Description: PGP signature
Hi!
I think we should plan for 0.2 within a month or so. Here are the
important features I’d like to see in:
• ‘guix pull’ (see TODO; I’ve started working on that);
• a simple “binary substituter”, which would allow pre-built binaries
to be transparently downloaded from trusted source,
21 matches
Mail list logo
