* gnu/packages/hash.scm (pfff): New variable.
---
gnu/packages/hash.scm | 29 +
1 file changed, 29 insertions(+)
create mode 100644 gnu/packages/hash.scm
diff --git a/gnu/packages/hash.scm b/gnu/packages/hash.scm
new file mode 100644
index 000..c3cbd85
--- /dev/
On 03/01/16 06:54, Ludovic Courtès wrote:
Ben Woodcroft skribis:
On 02/01/16 04:17, Ludovic Courtès wrote:
Ben Woodcroft skribis:
On 01/01/16 19:28, Pjotr Prins wrote:
On Fri, Jan 01, 2016 at 06:27:21PM +1000, Ben Woodcroft wrote:
It seems there's 30 packages to be updated, out of the
Sorry to bump an old thread but I agree with the OP that tags in
packages would be very helpful, and I can think of at least one use case
in which they might be necessary: games.
While game genre can be put into the description, games right now are
not all in the same .scm files (for example, gnom
Ben Woodcroft skribis:
> On 02/01/16 04:17, Ludovic Courtès wrote:
>> Ben Woodcroft skribis:
>>
>>> On 01/01/16 19:28, Pjotr Prins wrote:
On Fri, Jan 01, 2016 at 06:27:21PM +1000, Ben Woodcroft wrote:
> It seems there's 30 packages to be updated, out of the 107 in
> ruby.scm. Going
swedebu...@riseup.net skribis:
> ~/src/guix$ guix package -i gnupg:2.0.0 -r gnupg
> guix package: error: package `gnupg-2.1.10' lacks output `2.0.0'
The colon sign is (currently) used to delimit output names, not version
numbers. To select a version, use “gnupg-2.0” as Leo suggests. See the
doc
swedebu...@riseup.net skribis:
> In other GNU/Linux systems you have:
> cat /proc/version
> uname -a
> lsb_release -a
>
> I would like to document the equivalents for GuixSD, are these:
> cat /proc/version
> uname -a
> guix --version
>
> ?
I would argue that this is outside the scope of Gui
swedebu...@riseup.net writes:
> How do I best go about testing my changes to the build-system? make &
> ./pre-inst-env guix ...? Somebody mentioned input but I did not
> understand that.
Yes, “./pre-inst-env” allows you to use the guix library in the current
directory.
Note that when you chan
On 01/02/2016 12:10 PM, swedebu...@riseup.net wrote:
> On 2016-01-01 19:10, swedebu...@riseup.net wrote:
>> On 2015-12-30 23:00, Cyril Roelandt wrote:
>>> On 12/30/2015 08:53 PM, swedebu...@riseup.net wrote:
I am trying to fix this error in the pypi-importer:
>>>
>>> Could you send your fix as
On 2016-01-02 18:10, swedebu...@riseup.net wrote:
So removing the (else -> to a comment and adjusting the parentheses
did not work.
it did work with the right amount of parent.
Could somebody point me to relevant documentation about how to write
conditional statements in guile?
NWM doc here
On 2016-01-01 19:10, swedebu...@riseup.net wrote:
On 2015-12-30 23:00, Cyril Roelandt wrote:
On 12/30/2015 08:53 PM, swedebu...@riseup.net wrote:
I am trying to fix this error in the pypi-importer:
Could you send your fix as a unified diff? If you work from the git
repo, you can just run "git
On 2016-01-01 22:09, Leo Famulari wrote:
On Fri, Jan 01, 2016 at 09:35:40PM +0100, swedebu...@riseup.net wrote:
(trying to get gnupg to work knowing that ludo runs some 2.0 version)
~/src/guix$ guix package -i gnupg:2.0.0 -r gnupg
guix package: error: package `gnupg-2.1.10' lacks output `2.0.0'
On 02/01/16 01:10, Ludovic Courtès wrote:
Ricardo Wurmus skribis:
Ben Woodcroft writes:
On 31/12/15 03:26, Ludovic Courtès wrote:
Ben Woodcroft skribis:
On 29/12/15 15:46, Ben Woodcroft wrote:
Unfortunately none of these builds are reproducible because rubygems
in Guix generally aren
"guix package --show=foo" displays supported systems, but emacs
interface ("Guix Package Info" buffer) does not. The attached patch
fixes it. Also the shown systems are buttons that can be used to
display latest Hydra builds of the current package/system (unhappily
Hydra does not handle such quer
Ludovic Courtès (2016-01-01 18:53 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-12-30 18:40 +0300) wrote:
>
> [...]
>
>>> Could you in a separate commit prepare a NEWS entry for 0.9.1 that
>>> succinctly lists these differences?
>>
>> Sure. Is the attached patch sufficient? If i
Federico Beffa (2016-01-01 19:53 +0300) wrote:
> On Fri, Jan 1, 2016 at 5:28 PM, Alex Kost wrote:
>> Ludovic Courtès (2016-01-01 18:22 +0300) wrote:
>>
then we should definitely add code in a similar way to instruct emacs
to look in the right places (".../guix.d") for our emacs packages
Pjotr Prins writes:
> I just wrote a package for pfff. Should it go into Guix, and if so,
> what module should it belong in? md5sum and shaxsum are part of
> coreutils. I am thinking pfff should go into gnu/packages/hash.scm.
I think “hash.scm” would be a good location.
> (define-public pfff
16 matches
Mail list logo
