[Bjørn Forsman:
* wrap some long lines
* tweak meta attrs (don't repeat package name, s/meta.maintainer/meta.maintainers/)
* provide a version number (v2.0) for 'evemu' (for nix-env)
]
The one-liner gcc buildPhase doesn't work anymore, so I'm using upstream
Makefile instead. The Makefile needs a tiny patch to work (not nixpkgs
specific).
Also fixup path to 'sox' and espeak-data/ (runtime deps) by providing
full paths.
TODO:
Uhm, seems like espeakedit still wants espeak-data/ in $HOME, even
thought I've told it to use $espeak/share/espeak-data. Have to contact
upstream to get this fixed.
Workaround:
cp -r $(nix-build -A espeak)/share/espeak-data ~
chmod +w ~/espeak-data
This is going to be a dependency of the upcoming Gojim version 0.16, so
let's package it so it's easy to run release canidate versions using
overrideDerivation without much cruft.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
There are zillions of lines of the form
foo = callPackage ../bla/foo { };
in all-packages.nix. To get rid of this verbosity, you can now list
such packages in pkgs/auto-packages.nix. This is just a list of
package file names, e.g.
development/libraries/libogg
development/libraries/libvorbis
tools/archivers/gnutar
If the package needs non-default function arguments, or if its
intended attribute name is different from its file name, then you
cannot put it in auto-packages.nix and instead need to specify it in
all-packages.nix.
If Nix had a glob function (https://github.com/NixOS/nix/pull/235), we
could even get rid of auto-packages.nix and have package expressions
be discovered automatically. However, that might not be desirable
because of the need to traverse the file system to find packages we
may not even use.
This package requires a special build process that's not based on Cabal (see
<https://github.com/agocorona/haste-perch/issues/5>). Someone needs to figure
out how to compile and install this stuff in the context of Nix.
