| 13 Oct 2023 |
 Lorenz Leutgeb | * FWIW, what I don't like about this format is that it is incompatible with Git's tree-ish format :[<n>:]<path>.
See:
| 14:49:30 |
| Lorenz Leutgeb | * FWIW, what I don't like about this format is that it is incompatible with Git's tree-ish format <rev>:[<n>:]<path>.
See:
| 19:24:16 |
| 14 Oct 2023 |
|  chreekat changed their display name from chreekat (afk, sick) to chreekat. | 08:54:15 |
 asymmetric | i've been mentioned directly here, not sure why, but anyway: as the docs team, do we have anything to say in this regard? Or can I go ahead and say "No blockers from the doc team"?
I think it's a no-brainer but wanted to check with someone else first
| 12:46:54 |
| asymmetric | oh i see why:
https://github.com/NixOS/nixpkgs/tree/1af277b55ed1fd600bc917233c83c51d06e14b8f/maintainers/team-list.nix#L252 | 12:50:06 |
| asymmetric | two questions:
- can/should we sync this with the members on github?
- why are we
enableFeatureFreezePing = true?
| 12:51:16 |
| asymmetric | ok 2. makes sense after reading this, although it seems to me it should default to true | 13:26:04 |
| 15 Oct 2023 |
 nonuke | Hi all, here I am back asking for help. :)
| 07:41:06 |
| nonuke | I've managed to build my software, and if I want I can run it directly from result/bin directory.
| 07:41:43 |
| nonuke | I've added a installPhase:
installPhase = ''
mkdir -p $out/bin
cp $out/comictagger $/out/bin
'';
| 07:42:38 |
| nonuke | It gives me an error: | 07:42:51 |
| nonuke | cp: cannot stat '/nix/store/mk60dlmvk66lwylm6kcs6r0kpzf9ikgd-comictagger/comictagger': No such file or directory | 07:43:19 |
| nonuke | as a matter of fact, when I ls the path, there is no executable there...
What am I missing? | 07:44:29 |
 @johannes.kirschbauer:scs.ems.host | Als Antwort auf @fricklerhandwerk:matrix.org
This looks great. Still, as @roberth suggested elsewhere recently, we should not encourage using builtins to keep separation of concerns. I suggest rendering what you have to the Nixpkgs manual. It would also avoid getting into hairy consistency problems between Nix and Nixpkgs documentation. The nix.dev reference section should ideally consist only of links to the manuals, but some things are currently hard to do in an ideal way. Thanks. I think reference documentation must be complete first. Then wie can add opinionated help/practices like: „dont use Builtins in nixpkgs because…“
Not having the documentation in one place is not enjoyable for most users. Most of the time you just need to get it work first then you learn about how to do it the (maybe opinionated) right way. | 07:45:39 |
 Minijackson | hey there! Note that this channel is not a general help channel, unless it's about the documentation itself | 07:46:34 |
| nonuke | Sorry, I've just noticed I am writing on the wrong channel. | 07:46:48 |
