<{^_^}>
#101655 (by zimbatm, 1 hour ago, open): ruby: make the build reproducible
<NixBridge>
zimbatm[discord]: It's a shame that Dir.glob doesn't sort the files.
<NixBridge>
ryantm[discord]: Yay!
<NixBridge>
NobbZ[discord]: To be honest, I wouldn't expect similar operations to return a presorted list in other languages as well.
<NixBridge>
ryantm[discord]: https://r13y.com/ Ruby was one of the short list of remaining non-reproducible things
<NixBridge>
ryantm[discord]: Darn, nix itself is not reproducible?
<qyliss>
Looks like Docbook isn't
<NixBridge>
zimbatm[discord]: good news, this will be fixed once nix 3.0 is released since the doc is now markdown
<NixBridge>
NobbZ[discord]: 😦
<NixBridge>
ryantm[discord]: Overall this list is getting really short. Very exciting.
<NixBridge>
NobbZ[discord]: I'm not happy with that, RST or or ORG would have been much more to my liking. MD lacks features for writing technical documentation in my opinion and quite often requires escaping into inline HTML.
<NixBridge>
zimbatm[discord]: @NobbZ but is it an improvement over docbook? I feel like reaching the documentation format nirvana is never going to have 100% consensus
<NixBridge>
zimbatm[discord]: @ryantm agreed. And I would be surprised if reproducibility patches weren't already included in Debian or Guix to steal from.
<simpson>
It is best not to fight about which format the Nix docs are in. History has shown that it doesn't really matter that much, other than that changing the format changes the flavor of the arguments.
<qyliss>
when I looked a few days ago I tihnk *most* of the remaining failures were because of docbook
<NixBridge>
zimbatm[discord]: counting half a day per package, I could 9 days of work left
<NixBridge>
NobbZ[discord]: @zimbatm I have never written docbook consciously, so I can't say much about it.
<NixBridge>
zimbatm[discord]: in short: it has a rich semantic, and breaks if the writer doesn't follow it 100%
<NixBridge>
zimbatm[discord]: and Markdown is a baby syntax that renders all of the time, even when there is an issue
<NixBridge>
NobbZ[discord]: Well, RST and ORG are easy to break as well 😄 Also I can see why ORG is not to be used, it basically locks you to a certain editor to use all of its features…
<NixBridge>
zimbatm[discord]: most people should know Markdown by now, and can check the rendering on the pull request
<qyliss>
I see wrong markdown several times a week
<qyliss>
Usually it comes down to list indentation, which is extremely confusing
<NixBridge>
zimbatm[discord]: yeah
<qyliss>
And people must either not check the preview or just not care that their list is broken into two by a random flotaing paragraph in the middel
<NixBridge>
zimbatm[discord]: XML treats documentation like programming
<NixBridge>
zimbatm[discord]: if the list is broken, our brain can still somehow understand the doc, and send a PR to fix it afterwards
<NixBridge>
NobbZ[discord]: Which dialect is used for MD?
<NixBridge>
zimbatm[discord]: no idea
<NixBridge>
zimbatm[discord]: I would expect GFM
<NixBridge>
zimbatm[discord]: or at least CommonMark with table extensions
<NixBridge>
NobbZ[discord]: That would indeed something I could live with/write for.
<NixBridge>
zimbatm[discord]: anyways
<NixBridge>
zimbatm[discord]: r13y is more interesting to me
<NixBridge>
NobbZ[discord]: GFM modulo Issuelinking is basically what I expect everywhere.
<NixBridge>
NobbZ[discord]: Though I have already seen dialects that did links with `(label)[http://example.com]`…
<NixBridge>
NobbZ[discord]: Any I'm fine with switching the topic 😄
<NixBridge>
NobbZ[discord]: And I'm fine with switching the topic 😄
<qyliss>
hmm, the bridge communicates edits by just reposting the message
<qyliss>
without even a * indicator like Matrix to show it's an edit