... after auto-removing some kinds of files by default.
In some cases I let them be removed and in others I let them be put into
$docdev. That was more due to general indecisiveness on this question
than any reasons in the particular cases.
packages. Turns out that those packages set INSTALLDIRS=perl, so we
override it to INSTALLDIRS=site.
svn path=/nixpkgs/branches/stdenv-updates/; revision=15251
WTF is that the Perl module installation path suddenly has changed
from $out/lib/site_perl to $out/lib/perl5/site_perl. Investigating...
svn path=/nixpkgs/branches/stdenv-updates/; revision=15241
* Put the fix for Perl modules that install in the wrong location
($out/lib instead of $out/lib/site_perl) in the generic Perl
builder.
svn path=/nixpkgs/trunk/; revision=14051
to the propagated build inputs as a convenience to people who want
to install Perl packages into their user environments.
svn path=/nixpkgs/trunk/; revision=8278
* Remove explicit setting of PERL5LIB.
* Use the generic Perl builder for the BerkeleyDB and XML::Parser
modules.
* Prefix all names of Perl modules with `perl-' (in the generic Perl
builder).
svn path=/nixpkgs/trunk/; revision=2365
* MythTV: the setup program works :-).
* Added XmlTV. This requires a huge number of Perl modules, so...
* Added a generic builder for Perl modules. I'm lazy so the modules
are defined directly in all-packages-generic.nix. The generic
builder also patches Perl scripts to include a hard-coded Perl
module search path (i.e., similar to an RPATH in ELF executables).
svn path=/nixpkgs/trunk/; revision=2083
