samueldr changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS 19.09 is released! https://discourse.nixos.org/t/nixos-19-09-release/4306 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite | https://logs.nix.samueldr.com/nixos-dev
infinisi1 is now known as infinisil
drakonis_ has joined #nixos-dev
ixxie has quit [Ping timeout: 240 seconds]
ixxie has joined #nixos-dev
drakonis has joined #nixos-dev
justanotheruser has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis_ has quit [Ping timeout: 276 seconds]
drakonis1 has quit [Ping timeout: 250 seconds]
drakonis1 has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.6]
justanotheruser has quit [Ping timeout: 250 seconds]
justanotheruser has joined #nixos-dev
ixxie has quit [Ping timeout: 240 seconds]
drakonis1 has quit [Read error: Connection reset by peer]
drakonis1 has joined #nixos-dev
FRidh has joined #nixos-dev
Jackneill has joined #nixos-dev
alp- is now known as alp
__monty__ has joined #nixos-dev
<FRidh> with structured attributes the attributes are written to the file .attrs.json. This file is written with permissions 0666 and is thus writeable. Would it make sense to have it read-only? That way, if a derivation wants to store it, it could be guaranteed that it is untouched. I'm thinking here about the situation where we woul want to record this file in a separate output for traceability.
<niksnut> FRidh: making it read-only wouldn't guarantee that, since the directory is writable
<LnL> also seems similar to persisting or uploading the drv
<FRidh> that was the reason behind it actually. While you can say keep-derivations, I don't think you can say `nix copy` and include the .drv
<LnL> drvs can be uploaded to a cache, would be nice if hydra did that
pie_ has quit [Quit: No Ping reply in 180 seconds.]
pie_ has joined #nixos-dev
pie_ has quit [Ping timeout: 252 seconds]
psyanticy has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis has quit [Ping timeout: 240 seconds]
drakonis has joined #nixos-dev
<domenkozar[m]> hercules does that :)
<domenkozar[m]> turns out we needed to add batching support
<domenkozar[m]> since uploading 20k drvs takes time :D
<domenkozar[m]> (as you have to check the cache each evaluation)
drakonis has quit [Quit: WeeChat 2.6]
<globin> niksnut, FRidh: there actually is an issue with the .attrs.* files and moving stdenv to using structured attrs where i'm not sure how to proceed yet. if sourceRoot = "."; then the unpacking tries to chmod the whole dir including the .attrs files which fails, as they aren't owned by the build user
evanjs has quit [Quit: ZNC 1.7.4 - https://znc.in]
evanjs has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis1 has quit [Ping timeout: 276 seconds]
drakonis has quit [Quit: WeeChat 2.6]
drakonis1 has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis1 has quit [Ping timeout: 240 seconds]
pie_ has joined #nixos-dev
drakonis has quit [Ping timeout: 250 seconds]
drakonis has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
drakonis has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
ixxie has joined #nixos-dev
<niksnut> globin: hm, it should probably be owned by the build user
<LnL> I assumed it was pretty similar to how env-vars is created, does that happen somewhere else?
tilpner has quit [Quit: tilpner]
tilpner has joined #nixos-dev
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-dev
<niksnut> LnL: env-vars is created by the stdenv setup script
<niksnut> not by nix
red[evilred] has joined #nixos-dev
<red[evilred]> What actually does env-bars do?
<red[evilred]> I constantly see failed permissions on it when I do a nixos-rebuild but everything still seems to work regardless
<LnL> oh right, now that you mention it I remember struggling with that when working on a shell thing
<LnL> that happens in the child, so it automatically has the correct permissions
<worldofpeace> Jan Tojnar: I think the motivation there would be pretty simple
<jtojnar> worldofpeace is it clear for someone who is not a distro maintainer?
<worldofpeace> Jan Tojnar: No, distro maintainers live in a world of software and their giant dependencies 😁 People that write them just want the code to be good and useful.
<worldofpeace> I personally believe every programmer in the linux world should have a distro maintainer on call to tell them what not to do.
<jtojnar> main problem with this is that meson does not really support code re-use
capisce has quit [Ping timeout: 246 seconds]
capisce has joined #nixos-dev
psyanticy has quit [Quit: Connection closed for inactivity]
<worldofpeace> hmm, you're right. that might make it more complicated point to sell.
<ixxie> worldofpeace: maybe you should write a little guide and post it on hacker news with a clickbaity title like 'falsehood FOSS app devs believe about making their code portable'
drakonis_ has quit [Read error: Connection reset by peer]
<worldofpeace> ixxie: that's actually a great idea. Nix visibility could get boosted, if you need a guide how to make your code portable look no further than nixos.
<ixxie> worldofpeace: you mean, 'package your app for Nix and learn just how portable it is' sort of blogpost?
<worldofpeace> Jan Tojnar: #73378 looks good? I was planning on using that in the gnome-xorg test.
<{^_^}> https://github.com/NixOS/nixpkgs/pull/73378 (by worldofpeace, 1 week ago, open): nixos/gdm: make desktopManager.default work
<ixxie> worldofpeace: if you write it with an example walking through you packaging a real life app showing the pitfalls it could be a great read!
<worldofpeace> ixxie: I think people can't really see what sort of things we have to go through to actually port something for nixos, our platform reveals impurities.
<worldofpeace> ixxie: thanks. I'm thinking either writing something would be nice, or ooh even better. I could script and record it. And publish reading material as well.
<ixxie> worldofpeace: so enter NixOS and you are - so to speak - entering the gates of Heaven; you must be purified to pass the gates or enter DDL Hell.
<ixxie> (feel free to use that metaphor in the blog post xD)
v0|d has joined #nixos-dev
<worldofpeace> ixxie: 😆 that's fab. It'll begin with a slightly condescending farce, and then a well balanced perspective.
drakonis_ has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis_ has quit [Ping timeout: 265 seconds]
drakonis has quit [Ping timeout: 276 seconds]
<gchristensen> ,tell fridh to ping me
<{^_^}> gchristensen: I'll pass that on to fridh
<jtojnar> worldofpeace I do not like raising exceptions as state for flow control, but otherwise looks good
<jtojnar> worldofpeace by the way, did you read the GIMP discussion regarding fetching VCS archives?
<worldofpeace> Jan Tojnar: yeah, python kinda twists my brain in a strange way because I don't really prefer it. I could probably move that into main()
<jtojnar> We should probably modify fetchFromGitLab to accept keepDotGit like fetchFromGitLab does
<worldofpeace> Jan Tojnar: I don't think I have, link? Must say searching for GIMP can give you some rather unwanted results in duckduckgo. only now realize further why they want a name change 🤣
<worldofpeace> ugh, I don't like it when people do this with meson
drakonis has joined #nixos-dev
<jtojnar> except for one urbandictionary link I only see links for GNU Image Manipulation Program
<jtojnar> plus two Adobe ads
<jtojnar> as a non-native English speaker, I do not really understand the controversy, the program is the primary meaning for me
<adisbladis> jtojnar: If you know the other meaning the association is unfortunate (and makes searching for things without nsfw results hard)
<jtojnar> whereas glimpse evokes much less pleasant notions for me
drakonis1 has quit [Ping timeout: 276 seconds]
<jtojnar> I have safe search turned off and GIMP is one of the search terms that does not include porn for me in the results (at least until end of the second page)
<worldofpeace> Umm, the main argument there was because they can't figure out what git commit it was generated from Jan Tojnar? Literally have to give a git revision to gitlab api to get a tarball.
<jtojnar> worldofpeace also that they build from dist tarballs for testing
<jtojnar> so anything else is not sanctioned
<jtojnar> is the slur really that common? I do not recall encountering it before this controversy?
<worldofpeace> Jan Tojnar: I had no awareness of the work until reading about it. It's also not a convenient namechange either.
<worldofpeace> * word
<jtojnar> i.e. is that a meaning 90% of English speaker will be familiar with?
drakonis1 has joined #nixos-dev
<worldofpeace> lol, no. Perhaps deep urban dictionary readers.
<simpson> jtojnar: As a native of the USA, I'd estimate that about half of English-speakers know what a gimp is, or gimping or being gimped. They might not think of it as necessarily sexual.
<jtojnar> there is only so many combinations of letters in the alphabet that are not unpronouncable, every one of them will probably have something offensive associated with it eventually
drakonis1 has quit [Client Quit]
drakonis1 has joined #nixos-dev
<worldofpeace> Jan Tojnar: I agree. I think there's other things of important to appeal better to a different group than changing your name from an acryonym that might have this association.
<jtojnar> at least both groups are collaborating in this case
ixxie has quit [Ping timeout: 265 seconds]
ckauhaus has quit [Quit: WeeChat 2.6]
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
__monty__ has quit [Quit: leaving]
<jtojnar> hmm, should we allow recursive maintainer teams?
<infinisil> gchristensen: I think ,tell is case sensitive btw
<infinisil> Should probably fix that since nicks on freenode (or irc in general?) aren't case sensitive
<worldofpeace> Jan Tojnar: hmm, what if multiple teams share similar members that are added to the same package?
<jtojnar> yeah, that is another concern
<worldofpeace> exactly, so I might have to retract my comment with it maybe being merge ready. That's like to happen quickly, so we'll need some de-duplication.
<worldofpeace> * likely
<jtojnar> worldofpeace it is quite easy to do it consumer-side https://github.com/jtojnar/ofborg/pull/new/maintainer-groups
<jtojnar> though maybe we would want to have that code in nixpkgs so that it can be reused by all tools
justanotheruser has quit [Quit: WeeChat 2.6]
<thoughtpolice> It's incredibly annoying that buildRustPackage does not easily allow you to call overrideAttrs to override the cargoSha256.
<thoughtpolice> Ugh. That's going to be an annoying mass rebuild.