Age | Commit message (Collapse) | Author | Files | Lines |
|
Thanks to:
http://archmobile.org/trac/ticket/42
svn path=/nixpkgs/branches/armv5tel-linux/; revision=18003
|
|
svn path=/nixpkgs/branches/armv5tel-linux/; revision=18002
|
|
svn path=/nixpkgs/branches/armv5tel-linux/; revision=18001
|
|
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17998
|
|
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17997
|
|
svn merge -r 17288:17462 https://svn.nixos.org/repos/nix/nixpkgs/trunk
I know I should be merging from stdenv-updates... I'll try to get this branch
in sync with stdenv-updates soon.
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17463
|
|
svn path=/nixpkgs/trunk/; revision=17440
|
|
$out/share/PolicyKit/policy - otherwise we can't let PolicyKit find
the policies of other packages (such as HAL).
svn path=/nixpkgs/trunk/; revision=17438
|
|
svn path=/nixpkgs/trunk/; revision=17435
|
|
configure script prints out this ominous warning:
WARNING: PolicyKit is disabled. You need to manually edit the hal.conf
file to lock down the service. Failure to do so allows any
caller to make hald do work on their behalf which may be
a huge SECURITY HOLE. I repeat: YOU NEED TO EDIT THE FILE
hal.conf to match your distro/site to avoid NASTY SECURITY HOLES.
Note that HAL only builds with the old PolicyKit (it looks for
polkit.pc). Reverted ConsoleKit to the last version that used the
old PolicyKit for this reason.
svn path=/nixpkgs/trunk/; revision=17432
|
|
svn path=/nixpkgs/trunk/; revision=17426
|
|
a headache. "polkit" is the new, unstable release series.
"policykit" is the old series. (See
http://lists.freedesktop.org/archives/polkit-devel/2009-February/000106.html
for an "explanation" of the name change.) It seems that for HAL we
need to revert to the old "policykit", since it doesn't compile
against "polkit".
svn path=/nixpkgs/trunk/; revision=17425
|
|
svn path=/nixpkgs/trunk/; revision=17415
|
|
svn path=/nixpkgs/trunk/; revision=17407
|
|
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17384
|
|
svn path=/nixpkgs/trunk/; revision=17357
|
|
svn path=/nixpkgs/trunk/; revision=17347
|
|
svn path=/nixpkgs/trunk/; revision=17326
|
|
svn path=/nixpkgs/trunk/; revision=17323
|
|
svn path=/nixpkgs/trunk/; revision=17322
|
|
svn path=/nixpkgs/trunk/; revision=17320
|
|
svn path=/nixpkgs/trunk/; revision=17303
|
|
svn path=/nixpkgs/trunk/; revision=17299
|
|
svn path=/nixpkgs/trunk/; revision=17298
|
|
svn merge -r 17269:17288 https://svn.nixos.org/repos/nix/nixpkgs/trunk
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17289
|
|
svn path=/nixpkgs/trunk/; revision=17287
|
|
svn path=/nixpkgs/trunk/; revision=17282
|
|
svn path=/nixpkgs/trunk/; revision=17281
|
|
svn path=/nixpkgs/trunk/; revision=17276
|
|
svn path=/nixpkgs/trunk/; revision=17274
|
|
svn path=/nixpkgs/trunk/; revision=17271
|
|
I did:
svn merge -r 17114:17269 https://svn.nixos.org/repos/nix/nixpkgs/trunk
svn path=/nixpkgs/branches/armv5tel-linux/; revision=17270
|
|
svn path=/nixpkgs/trunk/; revision=17262
|
|
svn path=/nixpkgs/trunk/; revision=17250
|
|
svn path=/nixpkgs/trunk/; revision=17249
|
|
isn't the default yet.
svn path=/nixpkgs/trunk/; revision=17245
|
|
svn path=/nixpkgs/branches/stdenv-updates/; revision=17237
|
|
svn path=/nixpkgs/trunk/; revision=17228
|
|
svn path=/nixpkgs/trunk/; revision=17222
|
|
svn path=/nixpkgs/trunk/; revision=17221
|
|
- Added GPM support to midnight commander
svn path=/nixpkgs/trunk/; revision=17209
|
|
characters
svn path=/nixpkgs/trunk/; revision=17207
|
|
svn path=/nixpkgs/trunk/; revision=17196
|
|
svn path=/nixpkgs/trunk/; revision=17194
|
|
svn path=/nixpkgs/trunk/; revision=17187
|
|
svn path=/nixpkgs/branches/stdenv-updates/; revision=17167
|
|
in stdenvLinux.
svn path=/nixpkgs/branches/stdenv-updates/; revision=17152
|
|
static nss libs from glibc.
svn path=/nixpkgs/branches/stdenv-updates/; revision=17145
|
|
svn path=/nixpkgs/branches/stdenv-updates/; revision=17133
|
|
run some
of its programs at that stage, and if the glibc programs have been compiled with
-shared-libgcc (the default with a gcc built without --disable-shared), it will need
the libgcc_s.so.1 available exactly on the $out/lib path. The libc scripts force
the library-path calling directly its just built dynamic loader. Bootstrapping
gcc and glibc in the same 'prefix' would not need anything like this.
Btw, I think the postInstall phase doesn't work, because the glibc I got has still
this libgcc_s.so.1 in it. I've to check if the phase runs well or not, maybe on a
faster computer.
svn path=/nixpkgs/branches/stdenv-updates/; revision=17128
|