Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Lluís Batlle i Rossell
On Mon, Nov 19, 2012 at 08:18:52AM +0100, Mathijs Kwik wrote: Sure, no hurries. Let's say we wait a month or so, 3.7 will be out too. I will then ask again about 3.5 So do we all agree on the other ones being obsolete? As for me, for all I remember, yes. PS: I feel a bit awkward for

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Eelco Dolstra
Hi, On 19/11/12 07:11, Marc Weber wrote: Isn't it enough to depend on the git's hash value, No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256 hash of the expected contents. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Eelco Dolstra
Hi, On 18/11/12 20:58, Mathijs Kwik wrote: Indeed I didn't think about 2.6.35 being our current headers, so indeed we should keep 2.6.35 until stdenv-upgrades. FWIW, the stdenv branch already uses Linux 3.5.x for the kernel headers. -- Eelco Dolstra | LogicBlox, Inc. |

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Marc Weber
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:01:39 +0100 2012: No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256 hash of the expected contents. I know what the current implementation requires. Just wondering whether this should be relaxed for git (like) VCS

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Eelco Dolstra
Hi, On 19/11/12 11:25, Marc Weber wrote: Excerpts from Eelco Dolstra's message of Mon Nov 19 11:01:39 +0100 2012: No, because Nix's fixed-output derivation feature requires a md5/sha1/sha256 hash of the expected contents. I know what the current implementation requires. Just wondering

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Marc Weber
Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012: No. fetchgit won't work if it's not a fixed-output derivation, because it won't necessarily have network access (it might run in a chroot). Again: I'm not talking about the current state. I'm aware about how it works. I'm

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Joachim Schiele
- Original message - Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012: No.  fetchgit won't work if it's not a fixed-output derivation, because it won't necessarily have network access (it might run in a chroot). Again: I'm not talking about the current

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Shea Levy
Is it terribly difficult to run nix-prefetch-git? Built-in vcs-specific support doesn't strike me as simplification. On Nov 19, 2012, at 7:10 AM, Joachim Schiele j...@lastlog.de wrote: - Original message - Excerpts from Eelco Dolstra's message of Mon Nov 19 11:36:00 +0100 2012:

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Malcolm Matalka
Could fetchgit handle that on its own though? Also, at least for github, if you want to install a specific tag, which isn't always the case, you can link to the .zip copy of it from the github page. /M Shea Levy s...@shealevy.com writes: Is it terribly difficult to run nix-prefetch-git?

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Marco Maggesi
For the record, I still use 2.6.35 which is the newest kernel supporting BLCR presently available in NixoOS (BLCR needs kernels = 2.6.38). By the way, for what I can say, this makes NixOS the only distribution which currently supports easily BLCR (just add two lines in configuration.nix). Seems

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Marc Weber
Excerpts from Shea Levy's message of Mon Nov 19 13:38:37 +0100 2012: Is it terribly difficult to run nix-prefetch-git? YES: I'm talking about such configurations: http://gembundler.com/ And here you have git repo and hash. Trying to semi automatically package such things requires much overhead

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Mathijs Kwik
Marco Maggesi magg...@math.unifi.it writes: For the record, I still use 2.6.35 which is the newest kernel supporting BLCR presently available in NixoOS (BLCR needs kernels = 2.6.38). By the way, for what I can say, this makes NixOS the only distribution which currently supports easily BLCR

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Mathijs Kwik
Marc Weber marco-owe...@gmx.de writes: Excerpts from Shea Levy's message of Mon Nov 19 13:38:37 +0100 2012: Is it terribly difficult to run nix-prefetch-git? YES: I'm talking about such configurations: http://gembundler.com/ And here you have git repo and hash. Trying to semi automatically

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Lluís Batlle i Rossell
On Mon, Nov 19, 2012 at 02:26:00PM +0100, Mathijs Kwik wrote: Marco Maggesi magg...@math.unifi.it writes: For the record, I still use 2.6.35 which is the newest kernel supporting BLCR presently available in NixoOS (BLCR needs kernels = 2.6.38). By the way, for what I can say, this makes

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Mathijs Kwik
Lluís Batlle i Rossell vi...@viric.name writes: On Mon, Nov 19, 2012 at 02:26:00PM +0100, Mathijs Kwik wrote: Marco Maggesi magg...@math.unifi.it writes: For the record, I still use 2.6.35 which is the newest kernel supporting BLCR presently available in NixoOS (BLCR needs kernels =

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Eelco Dolstra
Hi, On 19/11/12 14:39, Lluís Batlle i Rossell wrote: As for glibc, the glibc has to be told the minimum kernel version to build for. It will use not all syscalls available in the headers, but only those which match the 'configure' argument requirement. But I imagine Eelco wants glibc to

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Lluís Batlle i Rossell
On Mon, Nov 19, 2012 at 03:25:08PM +0100, Eelco Dolstra wrote: Hi, On 19/11/12 14:39, Lluís Batlle i Rossell wrote: As for glibc, the glibc has to be told the minimum kernel version to build for. It will use not all syscalls available in the headers, but only those which match the

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Eelco Dolstra
Hi, On 19/11/12 15:28, Lluís Batlle i Rossell wrote: But I imagine Eelco wants glibc to be built for 3.5 kernels or above. Stdenv has --enable-kernel=2.6.35. Do you favour a higher value? Is there a good reason for a higher value? Certainly it can't be higher than 3.2 since that's our

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Mathijs Kwik
On Mon, Nov 19, 2012 at 3:37 PM, Eelco Dolstra eelco.dols...@logicblox.com wrote: Hi, On 19/11/12 15:28, Lluís Batlle i Rossell wrote: But I imagine Eelco wants glibc to be built for 3.5 kernels or above. Stdenv has --enable-kernel=2.6.35. Do you favour a higher value? Is there a good

Re: [Nix-dev] end-of-life kernels

2012-11-19 Thread Lluís Batlle i Rossell
On Mon, Nov 19, 2012 at 03:37:45PM +0100, Eelco Dolstra wrote: Hi, On 19/11/12 15:28, Lluís Batlle i Rossell wrote: But I imagine Eelco wants glibc to be built for 3.5 kernels or above. Stdenv has --enable-kernel=2.6.35. Do you favour a higher value? Is there a good reason for

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Marc Weber
A similar solution for rubygems would probably not be too hard. As rubygems itself is written in ruby, you can probably plug in to its dependency resolution and downloading capabilities so you can focus on generating the sha256 and the nix expression. If you still haven't got it: I worte

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Marc Weber
Excerpts from Eelco Dolstra's message of Mon Nov 19 16:31:26 +0100 2012: Why would you need a double fetch? After running fetchgit, the Git tree is in the Nix store and shouldn't be downloaded again unless you do a garbage collect in between. You're right about this. I want to make bundler

Re: [Nix-dev] fetchgit - why sha256 protection?

2012-11-19 Thread Michael Raskin
Of course running nix-prefetch-git is an option, however checking whether a store path representing { url = ..; hash = .. } already exists is harder. If you run nix-prefetch-git twice it will fetch twice (waste). I haven't looked for options. nix-store --check-validity $(nix-store -q --outputs