On 17-05-16 04:43pm, zimbatm wrote:
> How do you find back which git revision was used to produce a given NixOS
> profile?
In my case it’s built by a hydra and the system name contains a hash.
>
> Maybe nixos-rebuild should be extended to include that in the revision
> name, and if the git repo
Op 16 mei 2017 18:43 schreef "zimbatm" :
How do you find back which git revision was used to produce a given NixOS
profile?
At LumiGuide I use the following module for that:
{ config, lib, ... }:
with lib;
{
options.system = {
lumiRevision = mkOption {
On 16/05/17 17:43, zimbatm wrote:
> How do you find back which git revision was used to produce a given
> NixOS profile?
>
> Maybe nixos-rebuild should be extended to include that in the revision
> name, and if the git repo is dirty.
I'm planning to implement the reverse approach on my system:
How do you find back which git revision was used to produce a given NixOS
profile?
Maybe nixos-rebuild should be extended to include that in the revision
name, and if the git repo is dirty.
On Sat, 13 May 2017, 14:34 Profpatsch, wrote:
> On 17-05-13 12:25pm, Layus wrote:
>
On 17-05-13 12:25pm, Layus wrote:
> On 13/05/17 12:14, Leo Gaspard wrote:
> See the previous ML discussion on that topic where we proposed to keep it
> opt-in, but with an apt-out config line in the default configuration.nix.
> This may already be implemented.
The ones who don’t keep their
On 13/05/17 12:14, Leo Gaspard wrote:
On 05/13/2017 05:28 AM, Stefan Huchler wrote:
[...]
Do you know the reason why it defaults to false, cant think of any
disadvantage of that functionality. I mean nixos eats harddrive like
nearly no other distro. So saving space cant be the reason.
Some
On 05/13/2017 05:28 AM, Stefan Huchler wrote:
> [...]
> Do you know the reason why it defaults to false, cant think of any
> disadvantage of that functionality. I mean nixos eats harddrive like
> nearly no other distro. So saving space cant be the reason.
>
> Some sort of privacy concern?
With
Anotther solution shown in
https://mailman.science.uu.nl/pipermail/nix-dev/2017-April/023403.html
which has an advantage of copying related modules (assuming they belong to
same folder as configuration.nix)
2017-05-13 6:28 GMT+03:00 Stefan Huchler :
> Tomasz Czyż
Tomasz Czyż writes:
> https://nixos.org/nixos/options.html#configuration+copy
Thanks nice, could not belive that I am the first "genieus" that thought
on that.
Do you know the reason why it defaults to false, cant think of any
disadvantage of that functionality. I mean
https://nixos.org/nixos/options.html#configuration+copy
2017-05-12 22:57 GMT+01:00 Stefan Huchler :
> Hi,
>
> I find it always strange, that when I revert back or boot a older
> version of nixos, the configuration file has no version that reflected
> that version. So I
Hi,
I find it always strange, that when I revert back or boot a older
version of nixos, the configuration file has no version that reflected
that version. So I have to seperatly have to backup the
configuration.nix file.
Could there not be at least a backup of the config used in that
generation
11 matches
Mail list logo