<{^_^}>
nixos-weekly#85 (by domenkozar, 5 days ago, open): Call for Content: 2019/05
pie___ has joined #nixos-dev
pie__ has quit [Ping timeout: 245 seconds]
yl has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-dev
johanot has joined #nixos-dev
jtojnar has joined #nixos-dev
jtojnar has quit [Remote host closed the connection]
drakonis has quit [Quit: WeeChat 2.3]
garbas has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 240 seconds]
init_6 has joined #nixos-dev
init_6 has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
ivan has quit [Quit: lp0 on fire]
harrow has quit [Quit: Leaving]
harrow has joined #nixos-dev
ivan has joined #nixos-dev
drakonis1 has quit [Ping timeout: 245 seconds]
drakonis1 has joined #nixos-dev
timor has joined #nixos-dev
Synthetica has joined #nixos-dev
jtojnar has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
timor has quit [Ping timeout: 240 seconds]
johanot has quit [Quit: WeeChat 2.2]
<catern>
urgh, I'm trying to teach Hydra to support having a jobset whose jobset expression is just a literal string passed as one of its inputs (or configs or something), but it's not clear how to do it elegantly and backwards-compatibly
<catern>
(this would be handy for ad-hoc jobs, testing, etc)
<catern>
currently it finds the jobset expression via NIX_PATH, which means the jobset expression has to actually exist as a path on disk
<catern>
essentially hydra-eval-jobset is hardcoded to do a "import <$jobsetExprInputName/$jobsetExprPath>" (where those two variables are from the jobset configuration)
<catern>
I *guess* that it could be elegant if instead hydra-eval-jobset ran an arbitrary Nix expression coming from the jobset configuration; then those two configuration variables could be replaced with a single "jobset expression" configuration variable, which would normally contain "import <whateverinput/whateverpath>"
<catern>
but that's a lot more free-form which is not necessarily good, and also of course it's a totally unacceptable compatibility break
jtojnar has joined #nixos-dev
<catern>
but maybe "just eval this arbitrary nix expression which is in my jobset configuration" is a clean way to think about the design? it doesn't force you to be version-controlled, which is both good and bad... I guess another benefit is that you could maybe do CI on repositories which aren't set up with a release.nix, and haven't adopted Nix at all... thoughts?
garbas has joined #nixos-dev
orivej has quit [Ping timeout: 250 seconds]
yl has joined #nixos-dev
yl has quit [Ping timeout: 240 seconds]
yl has joined #nixos-dev
andi- has quit [Changing host]
andi- has joined #nixos-dev
Synthetica has quit [Quit: Connection closed for inactivity]
<clever>
gchristensen: there was something in nixpkgs, to null out timestamps in pyc files, but i cant remember where its defined, and i think its missed a file...
johanot has quit [Quit: WeeChat 2.2]
jtojnar has quit [Remote host closed the connection]