[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nix-dev
Subject:    [Nix-dev] [***SPAM***] Re: Using Nix to build embedded linux firmware
From:       7c6f434c () mail ! ru (Michael Raskin)
Date:       2012-05-22 6:20:09
Message-ID: E1SWiLK-0003rz-QP.7c6f434c-mail-ru () smtp8 ! mail ! ru
[Download RAW message or body]

>> Remote installation of packages:
>> ? ? ? ?As a follow-up thought to the last one, would it be possible
>> ? ? ? ?to update an installation remotely, with only a very limited set of
>> ? ? ? ?tools being present? I've looked at Disnix, and the README says
>> ? ? ? ?that all target hosts need to have Nix (and Nixpkgs) installed,
>> ? ? ? ?which is unfortunate but understandable given its intended
>> ? ? ? ?use case (server/cluster deployment).
>>
>> ? ? ? ?The Nix store file structure seems simple
>> ? ? ? ?enough to allow remote management. Is this correct?
>
>This is seemes correct to me.  If you don't plan to have Nix on board,
>you can just maintain the closure of the wanted systems on the remote
>and remove everything which is not listed in the closure of the
>systems.
>
>Nix can generate such closure, and Hydra (the buildfarm) can even be
>used to generate them.

I also think that with some work one could have on-device store mounted
via sshfs with store metadata on the controlling PC, and use import 
operation and gc operation of nix-store to manage package set.




[prev in list] [next in list] [prev in thread] [next in thread]