I hope noone is unhappy with enabling PAM bu default. Whover doesn't want PAM to
take care of authentication can still use the "password" configuration
directive.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Replacing SBCL upstream tracking expression with a new version in a new
format.
Minuses: gave up on defining everything in Nix language (now update
expression is a series of actions to do when downloading fresh release,
it is actually interpreted by shell), now Nix expression contains
meaningful whitespace (the area to regenerate is determined by the
line with a specific comment and the closing brace on the otherwise
empty line).
Plusses: only one extra file which could even be moved out-of-tree if
desired, clean semantics for traversing multiple links (it is not found
in either Debian uscan or Gentoo euscan), the main expression is in one
file and is less different from usual style.
beta: 23.0.1271.60 (build successful)
dev: 24.0.1312.2 (build successful after patching)
The development version needs a patch in order to build properly against
PulseAudio. Issue and origin of the patch can be found here:
http://crbug.com/157876
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The reason behind this is because /proc/acpi/event has long been deprecated in
kernel 2.6.24 and is only there far backwards-compatibility reasons. New ACPI
events are delivered by either the input layer or the netlink interface.
As we no longer use kernels down to 2.6.24, I guess it's safe to make this
switch.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This adapter causes the resulting binaries to have debug info and no
optimisations. Example use (in all-packages.nix):
foo = callPackage ./foo.nix {
stdenv = keepDebugInfo stdenv;
};
I'm not sure yet how to handle these upgrades.
Should we keep the old version around?
Should we only keep it around if other pkgs in nixpkgs depend on it?
Probably people develop their own projects (that are not in nixpkgs)
on top of these and we don't want to break these.
For now, I think it's best just to keep old versions around, but
update the (unversioned) link to the latest.
External projects should then depend on explicit version numbers if
they don't want stuff to break.
If a certain package has +5 versions in nixpkgs, we can clear out the
unuseful ones.
