Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dump output straight to stdout #10

Open
teto opened this issue Jul 29, 2023 · 1 comment
Open

dump output straight to stdout #10

teto opened this issue Jul 29, 2023 · 1 comment

Comments

@teto
Copy link

teto commented Jul 29, 2023

I've been trying to speed up the nextcloud updater script in nixpkgs NixOS/nixpkgs#244057 (comment) but I am limited by the opiniated choices made in nc4nix. Could nc4nix output to stdout its content ? the caller could then choose where to output the generated content via shell redirection ?
aka nc4nix > nc27.nix (and print errors to stderr).
This may be annoying if nc4nix is called for different versions of nextcloud but as mentioned here #8 maybe it would be more flexible to accept only one version, e.g. nc4nix 27 > nc27.nix and have the callee call several nc4nix in parallel.
Is there any advantage of the current infrastructure with nc4nix ? does it gain anything from having several versions in NEXTCLOUD_VERSIONS ?

@leonklingele
Copy link
Member

I see that nc4nix creates a $VERSION.json upon successful run in the current working directory, e.g. 28.json. This certainly isn't nice, but works fine for our intended purposes. Also it allows for concurrent updates of multiple version files (doesn't look like this is implemented as of now though).

Want to give this a try @teto?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants