Oh, I forgot about it.
Anyway, so far I need to distribute test scripts, not the production
software. It would be too slow to upload big bundle each time.
"nix-copy-closure" or "rsync" would reuse common files from previous
uploads.
On 3/2/17, David Kleuker wrote:
> Hello Volth,
>
> some days ag
Yes, "nix-store -qR ..." and then "rsync" seems a simple and promising solution.
Thank you!
On 3/2/17, Tomasz Czyż wrote:
> I assume you could do
> nix-store --export or nix-store --dump to prepare archive
> or you can query nix store for all dependnecies and with that list you can
> copy them us
Hello Volth,
some days ago https://github.com/matthewbauer/nix-bundle was mentioned on the
ML.
I havn't tested it, so i can't say how mature and stable it is, but it should
be exactly what you are looking for.
When you have tested it, i would like to know if it works for you.
kind regards
dav
Also, somebody mentioned https://github.com/matthewbauer/nix-bundle
recently which is nice way to distribute some software to non nix
environments.
2017-03-02 16:49 GMT+00:00 Bjørn Forsman :
> On 2 March 2017 at 17:38, Volth wrote:
> > Hello
> >
> > What is a good way to copy a closure to a Linu
I assume you could do
nix-store --export or nix-store --dump to prepare archive
or you can query nix store for all dependnecies and with that list you can
copy them using method of your choice
2017-03-02 16:38 GMT+00:00 Volth :
> Hello
>
> What is a good way to copy a closure to a Linux machine
On 2 March 2017 at 17:38, Volth wrote:
> Hello
>
> What is a good way to copy a closure to a Linux machine where Nix is
> not installed (and it is tricky to install: 1. there is only root
> account and 2. there may be no Internet access) ?
>
> "nix-copy-closure" expects "nix-store" on the target m
Hello
What is a good way to copy a closure to a Linux machine where Nix is
not installed (and it is tricky to install: 1. there is only root
account and 2. there may be no Internet access) ?
"nix-copy-closure" expects "nix-store" on the target machine.
Would "nix-store" be a single executable wi