Re: [Nix-dev] systemd branch broken?

2013-01-10 Thread Lluís Batlle i Rossell
On Thu, Jan 10, 2013 at 12:19:10AM +0100, Eelco Dolstra wrote: > On 09/01/13 22:49, Peter Simons wrote: > > > after updating my installation to the current version of the systemd branch > > (b5e639dbb10c396e174aa79f5941c727675148d5), I can no longer log in. > > Maybe your Nixpkgs tree is not up

Re: [Nix-dev] systemd branch broken?

2013-01-10 Thread Eelco Dolstra
Hi, On 10/01/13 01:47, Peter Simons wrote: > > Maybe your Nixpkgs tree is not up to date? NixOS-systemd requires systemd > 197. > > I was using systemd 197 in those tests. I re-built my system with the current > heads from NixOS/systemd and both Nixpkgs/master and Nixpkgs/systemd, but the > is

Re: [Nix-dev] reproducable systems at a (much) later point / archive.org

2013-01-10 Thread Vladimír Čunát
On 01/09/2013 10:19 PM, Ludovic Courtès wrote: Florian Friesdorf skribis: Given that nix would support a "last-resort mirror" and given we could convince some instution (e.g. archive.org) to provide such a mirror, the world would be always able to exactly reproduce software installations and w

[Nix-dev] understanding Nix: dependencies

2013-01-10 Thread Christopher Howard
A few questions, to help me understand how Nix works: Nix being a fully deterministic package management system, does that mean that the exact dependencies required by each package are fixed, i.e. do not change over time for a specific package (version)? Does that include the dependencies of those

Re: [Nix-dev] understanding Nix: dependencies

2013-01-10 Thread Shea Levy
On 01/10/2013 02:02 PM, Christopher Howard wrote: A few questions, to help me understand how Nix works: Nix being a fully deterministic package management system, does that mean that the exact dependencies required by each package are fixed, i.e. do not change over time for a specific package (ve

Re: [Nix-dev] understanding Nix: dependencies

2013-01-10 Thread Vladimír Čunát
On 01/10/2013 08:07 PM, Shea Levy wrote: The long answer is: Currently, the way we build most of our packages the build time dependencies (e.g. where do I get my library headers) and the run time dependencies (e.g. which library do I link to) are the same, so updating the run time dependencies wi

[Nix-dev] Nix dependencies

2013-01-10 Thread Vladimír Čunát
Hi. This is a follow-up, but it considers a long-term thoughts of mine about nix package management evolution. I'll be glad to read your opinions. On 01/10/2013 08:26 PM, Vladimír Čunát wrote: there are external-runtime dependencies (let me call them that), like executables from other package

Re: [Nix-dev] reproducable systems at a (much) later point / archive.org

2013-01-10 Thread Bjørn Forsman
On 9 January 2013 10:27, Florian Friesdorf wrote: > Bjørn Forsman writes: >> On 9 January 2013 07:38, Florian Friesdorf wrote: >> [...] >>> Thoughts? >> >> I really like it. I think supporting additional source mirrors is a >> must-have feature :-) >> >> I have a long term plan to use NixOS for

[Nix-dev] [***SPAM***] modification time

2013-01-10 Thread Christopher Howard
Thank you every one for being patient in answering my many questions. There is another one of some practical significance to me: Would there be any negative effects that would result for altering the modification time for any of the files in the Nix installation, the nix store, or the nix state dir

Re: [Nix-dev] modification time

2013-01-10 Thread Marc Weber
Why not just try it? Executables should run no matter which timestamp they have. Of course nobody prevents executables to fail if their timestamp is older than a particular date. It doesn't make sense to implement such behaviour so I expect most things to work. Marc Weber