In reply to @linus:schreibt.jetzt
Rick (Mindavi): did you look at alternative UUID implementations when you were fixing UUID4-Tiny for aarch64? I seem to remember an alternative being mentioned somewhere, but don't remember what it was...

In reply to @k900:0upti.me
OK whomst do I poke here to get https://github.com/NixOS/hydra/pull/1243 merged

In reply to @andreas.schraegle:helsinki-systems.de
das_j

In reply to @k900:0upti.me
OK whomst do I poke here to get https://github.com/NixOS/hydra/pull/1243 merged

In reply to @k900:0upti.me
Bump

I haven't used Hydra much and have a question to see whether it might be a suitable tool for my usecase. I maintain a repository which defines some FPGA-targets for an embedded OS and I am providing pre-built FPGA bitstreams for these targets, so people don't have to install the heavyweight proprietary FPGA toolchains (>= 50GB binary blob) themselves.

I'm already building all of this with Nix, but using regular CI infrastructure like GitHub Actions or TravisCI to automate this is infeasible (can't redistribute the binary blob and it exceeds CI resource limitations).

If I were to build this with Hydra, can I

1. manually add the proprietary toolchain to the build system's nix-store as a garbage collector root and have Hydra use that for its builds, and
2. instruct Hydra to not offer / publish the proprietary toolchain itself? While it should be perfectly legal to compile a bitstream and redistribute that final artifact, I am not allowed to redistribute the toolchain itself. I do want to make the final artifacts available somewhere, although that doesn't have to be through Hydra directly.

1. required file
2. not easily