Ludovic Courtès wrote ..
> Perhaps we should ask savannah-hackers for a secondary Git repo?
I don't suppose there's any harm in that, except that it means using
Git but I'll go be quiet now.
Am Mittwoch, 23. Januar 2013 schrieb Ludovic Courtès:
> And what if you roll back once you’re at the empty profile?
Then nothing should happen.
> It seems more intuitive for me to error out like this, because there was
> really nothing but nothingness before “hello” was installed. :-)
> WDYT?
N
Andreas Enge skribis:
> $ guix-build libjpeg
> fails:
>
> Backtrace:
> In ice-9/boot-9.scm:
> 149: 12 [catch #t # ...]
> 157: 11 [#]
> In unknown file:
>?: 10 [catch-closure]
> In ice-9/boot-9.scm:
> 63: 9 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 407: 8 [eval # #]
> In unkno
Andreas Enge skribis:
> Am Montag, 21. Januar 2013 schrieb Ludovic Courtès:
>> Andreas Enge skribis:
>> > Is this not exactly how bsd-style operates?
>> Yes, but it’s only for BSD-style licenses.
>
> Finally I think we agree.
Nitpicking is what I do on my spare time. ;-)
> I was suggesting to
> Thanks, that worked. Here is a second version of the patch, which seems to
> work.
Applied, thanks!
I took the liberty to change the following:
> +(inputs
> + `(("perl", perl)
> + ))
No hanging parenthesis, and comma right before ‘perl’.
> +(home-page "http://www.ocaml.org/
Andreas Enge skribis:
> $ guix-package -i hello
>
> This creates a link $HOME/.guix-profile to $PERUSER/guix-profile; the
> latter points to the newly created $PERUSER/guix-profile-1-link
>
> $ guix-package --roll-back
> error: no previous profile; not rolling back
>
> No links are changed. I th
Hi Jason,
"Jason Self" skribis:
> Another option might be GNU Recutils.
Right.
> Regardless of the use of Org-mode or Recutils, is there any reason
> such a file couldn't exist in version control on Savannah? It could be
> part of either the source code repository or web pages repository.
> Ac
Hi!
With commit 21c203a, the ‘arguments’ field of packages is automatically
“thunked”–i.e., wrapped in a zero-argument closure. This allows the
value of ‘arguments’ to refer to the ‘%current-system’ fluid to do all
things system-specific.
Previously, when the value of ‘arguments’ was system-depe
> You also need ‘--without-bash-malloc’ (see ‘bash-light’ in bash.scm).
# ./configure --enable-static-link \
--without-bash-malloc \
--disable-readline \
--disable-history \
--disable-help-builtin \
--disable-progcomp \
By mistake, I just tried the following:
guix-package install freetype
Nothing happens, but an error message would still be useful.
Andreas
Rollback does not quite work as expected for me. I am starting without
.guix-profile in the home directory, and an empty directory
$PREFIX/var/nix/profiles/per-user/$USER (which I will shorten to $PERUSER
in the following).
$ guix-package -i hello
This creates a link $HOME/.guix-profile to $PE
Nikita Karetnikov skribis:
>> ‘guix-build’ is for packagers, when you want to build something without
>> actually adding it to your profile, whereas ‘guix-package -i’ is for
>> when you want to add something to your profile.
>
>> Do you think this should be clarified somehow?
>
> Yes. Could you
Am Dienstag, 22. Januar 2013 schrieb Ludovic Courtès:
> Commit 5401dd7 does that.
It almost works now, thanks! I can do
$ guix-build libjpeg-8d
and
$ guix-build libjpeg-9
but
$ guix-build libjpeg
fails:
Backtrace:
In ice-9/boot-9.scm:
149: 12 [catch #t # ...]
157: 11 [#]
In unknown file:
?:
* gnu/packages/ocaml.scm: New file.
* Makefile.am (MODULES): Add it.
* guix/licenses.scm: New variable.
---
On 01/21/2013 09:18 PM, Ludovic Courtès wrote:
> Alternately, you could move the ‘check’ phase after the install phase,
> like this (untested):
Thanks, that worked. Here is a second version
Am Montag, 21. Januar 2013 schrieb Ludovic Courtès:
> Andreas Enge skribis:
> > Is this not exactly how bsd-style operates?
> Yes, but it’s only for BSD-style licenses.
Finally I think we agree. I was suggesting to create something analogous to
bsd-style, just with a different name. But maybe bs
Ludovic Courtès wrote ..
> Another option would be to have a simple Org-mode file in a repo hosted
> on hydra.gnu.org (say), but that means that everyone would need to have
> an SSH account on that machine (unless we can use a single SSH account
> for everyone who needs to access the repo?).
>
> S
Nikita Karetnikov skribis:
>> I realize this is a bit more involved than “just” packaging the thing,
>> but it will be useful in the long run.
>
> I'm missing the big picture. That's the main problem. What will happen
> when I run 'guix-package -i hello'?
‘build-system’ objects are an abstract
Nikita Karetnikov skribis:
>> Could be, though it’s really inconvenient (heavyweight, browser-only).
>
> There are some bug trackers that support email [1]. Have you ever tried
> them?
Yes, http://bugs.gnu.org is a Debbugs instance, used by Guile, among others.
It’s convenient for bug reports,
Nikita Karetnikov skribis:
>> I'll try to build statically-linked Bash.
>
> Could anyone advise on this? Which flags and options should be used?
>
> The ones from the corresponding recipe look a bit complex for me. I
> tried this instead:
>
> # ./configure --enable-readline --enable-static-link
Hi,
Nikita Karetnikov skribis:
>> Wild guess: you’re building outside of a chroot, and Perl’s configure
>> found /usr/lib/libgdbm.so, so it decided to link against it, which
>> didn’t work because our linker doesn’t look for libraries there.
>
>> Can you confirm?
>
>> Solution: add “build-use-ch
> Instead, you can directly build the list of matching packages, like:
> (fold-packages (lambda (package result)
>(if (or (regexp-exec rx (package-synopsis package))
>(regexp-exec rx (package-description package)))
>(cons pa
Hi Alex,
Alex Sassmannshausen skribis:
> Whilst reading the published manual on the GNU Guix website I came across the
> following three sentences that could maybe be improved (their all in section
> 3.1):
> 'Instead of referring to these directories, users have their own profile,
> which poi
22 matches
Mail list logo
