AngryAnt, 3 months ago (edited 3 months ago)

@blair_fix If you're still considering edits, I would suggest wrapping your python 2/3 hashbang illustration story line with nix-shell hashbang examples. IE:

Python 2:

#!/usr/bin/env nix-shell  
#!nix-shell -i bash -p python2  

Python 3:

#!/usr/bin/env nix-shell  
#!nix-shell -i bash -p python3  

More complex environment description in a companion nix file (maybe more of an appendix thing):

#!/usr/bin/env nix-shell  
#!nix-shell -i bash more-detailed-environment.nix --pure  

AngryAnt, 3 months ago

@blair_fix For example, here's one for running a race car:
https://gitlab.com/framebunker/framebunker.Nix.BuildAgent/-/blob/Automated/LatestUpdate/unity-cli-shell.nix?ref_type=heads

adingbatponder, 3 months ago

@AngryAnt @blair_fix Sorry to be dim.. but I would like to try this out... but do not know what it does.... any clues welcome... does it go into configuration.nix .... ?

AngryAnt, 3 months ago

@adingbatponder @blair_fix Those specific hashbangs go as the first lines of a shell script.

When run on NixOS or nix-enabled macOS/Linux, nix will first resolve an environment with the specified packages available (or to the specifications of the referenced nix file) and then run the script in that environment.

At work we launch all our in-house tools that way - for guaranteed consistent cross-platform dependency resolution. The shell script just goes right in the tool source repository.

adingbatponder, 3 months ago

@AngryAnt @blair_fix sure thanks, but the untiy-cli-shell thing... what am I looking at there ? does that all go in the configuration.nix ? what does it do...

AngryAnt, 3 months ago

@adingbatponder @blair_fix Ah if you check the parent directory there's a utility which scans a Unity editor install path and generates a wrapper script for each version found. Those scripts reference this nix file.

The use case is a TeamCity build agent able to use its default integration to run editors installed via the Unity launcher.