| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All JARs in $pkg/share/java (for each $pkg in the build inputs) are
added to $CLASSPATH. Thus, you can say
buildInputs = [ setJavaClassPath someJavaDependency ];
and the JARs in someJavaDependency will be found automatically by
tools like javac or ant.
Note that the manual used to say that JARs should be installed in
lib/java; this is now share/java, following the Debian policy:
http://www.debian.org/doc/packaging-manuals/java-policy/x110.html
The directory share/java makes more sense because JARs are
architecture-independent. (Also, a quick grep shows that we were not
exactly consistent about this in Nixpkgs.)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also:
- It's now installable by doing "nix-env -i nix-generate-from-cpan".
- It maps dependencies to the correct attribute (e.g. HTML::HeadParser
is mapped to HTMLParser).
- It automatically selects buildPerlPackage or buildPerlModule.
- It's documented in the manual.
|
| |
|
| |
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=34062
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=18419
|
| |
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=15718
|
|
|
|
|
|
|
| |
now that Perl packages are in their own namespace
(perlPackages.<pkg>).
svn path=/nixpkgs/trunk/; revision=15176
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=15173
|
|
svn path=/nixpkgs/trunk/; revision=15124
|