jiebi/CodeConvo huggingface dataset:
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: <itemizedlist> <listitem> <para> <ins> Top-level <literal>idea</literal> package collection was renamed. All JetBrains IDEs are now at <literal>jetbrains</literal>. </ins> </para> </listitem> </itemizedlist>
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: <del> { stdenv, fetchurl, makeDesktopItem, makeWrapper, patchelf, p7zip , coreutils, gnugrep, which, git, python, unzip }: { name, product, version, src, wmClass, jdk, meta } @ attrs: with stdenv.lib; let loName = toLower product; hiName = toUpper product; execName = concatStringsSep "-" (init (splitString "-" name)); in with stdenv; lib.makeOverridable mkDerivation rec { inherit name src meta; desktopItem = makeDesktopItem { name = execName; exec = execName; comment = lib.replaceChars ["n"] [" "] meta.longDescription; desktopName = product; genericName = meta.description; categories = "Application;Development;"; icon = execName; extraEntries = '' StartupWMClass=${wmClass} ''; }; buildInputs = [ makeWrapper patchelf p7zip unzip ]; patchPhase = '' get_file_size() { local fname="$1" echo $(ls -l $fname | cut -d ' ' -f5) } munge_size_hack() { local fname="$1" local size="$2" strip $fname truncate --size=$size $fname } interpreter=$(echo ${stdenv.glibc.out}/lib/ld-linux*.so.2) if [ "${stdenv.system}" == "x86_64-linux" ]; then target_size=$(get_file_size bin/fsnotifier64) patchelf --set-interpreter "$interpreter" bin/fsnotifier64 munge_size_hack bin/fsnotifier64 $target_size else target_size=$(get_file_size bin/fsnotifier) patchelf --set-interpreter "$interpreter" bin/fsnotifier munge_size_hack bin/fsnotifier $target_size fi ''; installPhase = '' mkdir -p $out/{bin,$name,share/pixmaps,libexec/${name}} cp -a . $out/$name ln -s $out/$name/bin/${loName}.png $out/share/pixmaps/${execName}.png mv bin/fsnotifier* $out/libexec/${name}/. jdk=${jdk.home} item=${desktopItem} makeWrapper "$out/$name/bin/${loName}.sh" "$out/bin/${execName}"  --prefix PATH : "$out/libexec/${name}:${stdenv.lib.makeBinPath [ jdk coreutils gnugrep which git ]}"  --set JDK_HOME "$jdk"  --set ${hiName}_JDK "$jdk"  --set ANDROID_JAVA_HOME "$jdk"  --set JAVA_HOME "$jdk" ln -s "$item/share/applications" $out/share ''; } </del>
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: <ins> { stdenv, fetchurl, makeDesktopItem, makeWrapper, patchelf, p7zip , coreutils, gnugrep, which, git, python, unzip }: { name, product, version, src, wmClass, jdk, meta } @ attrs: with stdenv.lib; let loName = toLower product; hiName = toUpper product; execName = concatStringsSep "-" (init (splitString "-" name)); in with stdenv; lib.makeOverridable mkDerivation rec { inherit name src meta; desktopItem = makeDesktopItem { name = execName; exec = execName; comment = lib.replaceChars ["n"] [" "] meta.longDescription; desktopName = product; genericName = meta.description; categories = "Application;Development;"; icon = execName; extraEntries = '' StartupWMClass=${wmClass} ''; }; buildInputs = [ makeWrapper patchelf p7zip unzip ]; patchPhase = '' get_file_size() { local fname="$1" echo $(ls -l $fname | cut -d ' ' -f5) } munge_size_hack() { local fname="$1" local size="$2" strip $fname truncate --size=$size $fname } interpreter=$(echo ${stdenv.glibc.out}/lib/ld-linux*.so.2) if [ "${stdenv.system}" == "x86_64-linux" ]; then target_size=$(get_file_size bin/fsnotifier64) patchelf --set-interpreter "$interpreter" bin/fsnotifier64 munge_size_hack bin/fsnotifier64 $target_size else target_size=$(get_file_size bin/fsnotifier) patchelf --set-interpreter "$interpreter" bin/fsnotifier munge_size_hack bin/fsnotifier $target_size fi ''; installPhase = '' mkdir -p $out/{bin,$name,share/pixmaps,libexec/${name}} cp -a . $out/$name ln -s $out/$name/bin/${loName}.png $out/share/pixmaps/${execName}.png mv bin/fsnotifier* $out/libexec/${name}/. jdk=${jdk.home} item=${desktopItem} makeWrapper "$out/$name/bin/${loName}.sh" "$out/bin/${execName}"  --prefix PATH : "$out/libexec/${name}:${stdenv.lib.makeBinPath [ jdk coreutils gnugrep which git ]}"  --prefix LD_LIBRARY_PATH : "${stdenv.lib.makeLibraryPath [ # Some internals want libstdc++.so.6 stdenv.cc.cc.lib ]}"  --set JDK_HOME "$jdk"  --set ${hiName}_JDK "$jdk"  --set ANDROID_JAVA_HOME "$jdk"  --set JAVA_HOME "$jdk" ln -s "$item/share/applications" $out/share ''; } </ins>
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: gnustep-make = gnustep.make; # added 2016-7-6 htmlTidy = html-tidy;  # added 2014-12-06 iana_etc = iana-etc;  # added 2017-03-08 <ins> idea = jetbrains; # added 2017-04-03 </ins> inherit (haskell.compiler) jhc uhc;   # 2015-05-15 inotifyTools = inotify-tools; joseki = apache-jena-fuseki; # added 2016-02-28
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: libart = pkgs.gnome2.libart_lgpl; }; <del> idea = recurseIntoAttrs (callPackages ../applications/editors/idea { androidsdk = androidsdk_extras; }); </del> <ins> jetbrains = recurseIntoAttrs (callPackages ../applications/editors/jetbrains { androidsdk = androidsdk_extras; }); </ins> libquvi = callPackage ../applications/video/quvi/library.nix { };
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: <ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.15.2"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.15/${name}.tar.xz"; sha256 = "0g71zq6dpqrw2f40wfzdf18fdw41ymr17laqniy2kr622hkxdi8w"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: <ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.16.1"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.16/${name}.tar.xz"; sha256 = "1n708n9ixyy9qrzyv1wf4ybvcclx43ib9ki028wwpvkz6kv8zqlb"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { <del> name = "vala-0.14.2"; </del> <ins> version = "0.17.2"; name = "vala-${version}"; </ins> src = fetchurl { <del> url = mirror://gnome/sources/vala/0.14/vala-0.14.2.tar.xz; sha256 = "1l5kllw9vpwv24lzv9fp64l3sad46wpxgvsgryrwlrjg91w6jzl0"; </del> <ins> url = "mirror://gnome/sources/vala/0.17/${name}.tar.xz"; sha256 = "09i2s0dwmrk147ind2dx7nq845g12fp6fsjqrphhrr0dbi0zzgh3"; </ins> }; buildNativeInputs = [ yacc flex pkgconfig xz ];
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; <ins> license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; </ins> }; }
Code change:
JetBrains IDEs are currently at which is kind of confusing because the packages here aren't all under name. For example WebStorm, PhpStorm, PyCharm and so on - these are properties of JetBrains. Therefore I think it will be good to move all them under and rename to .
Do you want to make a pull request?

Related discussion:
text: urweb = callPackage ../development/compilers/urweb { }; <del> vala = callPackage ../development/compilers/vala { }; </del> <ins> vala = vala17; vala15 = callPackage ../development/compilers/vala/15.2.nix { }; vala16 = callPackage ../development/compilers/vala/16.1.nix { }; vala17 = callPackage ../development/compilers/vala/default.nix { }; </ins> visualcpp = callPackage ../development/compilers/visual-c++ { };
Code change:
tries to send (empty) md5 hashes to fetchurl, which doesn't accept md5 hashes it seems Steps to reproduce the behavior: enter the following command: The firefox plugin builds successfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --git revision tags of both NUR and nixpkgs are in the command given above
Can you try , I tested with your repro cmd changing to in nixpkgs src with the patch.
This works correctly, thank you very much!

Related discussion:
text: { name , url ? null <del> , md5 ? "" </del> , sha1 ? "" , sha256 ? "" , sha512 ? ""
Code change:
tries to send (empty) md5 hashes to fetchurl, which doesn't accept md5 hashes it seems Steps to reproduce the behavior: enter the following command: The firefox plugin builds successfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --git revision tags of both NUR and nixpkgs are in the command given above
Can you try , I tested with your repro cmd changing to in nixpkgs src with the patch.
This works correctly, thank you very much!

Related discussion:
text: source = if url == null then src else fetchurl { url = url; <del> inherit md5 sha1 sha256 sha512 hash; </del> <ins> inherit sha1 sha256 sha512 hash; </ins> }; in stdenv.mkDerivation {
Code change:
Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )

Related discussion:
text: This syntax is taken from [MyST](https://myst-parser.readthedocs.io/en/latest/using/syntax.html#targets-and-cross-referencing). <ins> #### HTML Inlining HTML is not allowed. Parts of the documentation gets rendered to various non-HTML formats, such as man pages in the case of NixOS manual. </ins> #### Roles If you want to link to a man page, you can use `` {manpage}`nix.conf(5)` ``. The references will turn into links when a mapping exists in [`doc/manpage-urls.json`](./manpage-urls.json).
Code change:
Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )

Related discussion:
text: _Default:_ the output path's hash. ``` <ins> #### Examples To define a referenceable figure use the following fencing: ```markdown :::{.example #an-attribute-set-example} # An attribute set example You can add text before ```nix { a = 1; b = 2;} ``` and after code fencing ::: ``` Defining examples through the `example` fencing class adds them to a "List of Examples" section after the Table of Contents. Though this is not shown in the rendered documentation on nixos.org. #### Figures To define a referencable figure use the following fencing: ```markdown ::: {.figure #nixos-logo} # NixOS Logo ![NixOS logo](./nixos_logo.png) ::: ``` Defining figures through the `figure` fencing class adds them to a `List  of Figures` after the `Table of Contents`. Though this is not shown in the rendered documentation on nixos.org. #### Footnotes To add a foonote explanation, use the following syntax: ```markdown Sometimes it's better to add context [^context] in a footnote. [^context]: This explanation will be rendered at the end of the chapter. ``` #### Inline comments Inline comments are supported with following syntax: ```markdown <!-- This is an inline comment --> ``` The comments will not be rendered in the rendered HTML. #### Link reference definitions Links can reference a label, for example, to make the link target reusable: ```markdown ::: {.note} Reference links can also be used to [shorten URLs][url-id] and keep the markdown readable. ::: [url-id]: https://github.com/NixOS/nixpkgs/blob/19d4f7dc485f74109bd66ef74231285ff797a823/doc/README.md ``` This syntax is taken from [CommonMark](https://spec.commonmark.org/0.30/#link-reference-definitions). #### Typographic replacements Typographic replacements are enabled. Check the [list of possible replacement patterns check](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15). </ins> ## Getting help If you need documentation-specific help or reviews, ping [@NixOS/documentation-reviewers](https://github.com/orgs/nixos/teams/documentation-reviewers) on your pull request.
Code change:
Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )

Related discussion:
text: # Contributing to this manual {#chap-contributing} <del> The [DocBook] and CommonMark sources of the NixOS manual are in the [nixos/doc/manual](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the [Nixpkgs](https://github.com/NixOS/nixpkgs) repository. </del> <ins> The sources of the NixOS manual are in the [nixos/doc/manual](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the [Nixpkgs](https://github.com/NixOS/nixpkgs) repository. </ins> This manual uses the [Nixpkgs manual syntax](https://nixos.org/manual/nixpkgs/unstable/#sec-contributing-markup). You can quickly check your edits with the following:
Code change:
Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )

Related discussion:
text: ## Building the Manual {#sec-writing-docs-building-the-manual} <del> The DocBook sources of the [](#book-nixos-manual) are in the </del> <ins> The sources of the [](#book-nixos-manual) are in the </ins> [`nixos/doc/manual`](https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual) subdirectory of the Nixpkgs repository.
Code change:
The wrapper only has , so the corresponding where would check for manpages is absent. don't have regular vim installed install something like 09pre104936.
You can find a fix in /

Related discussion:
text: inherit vimrcFile; # shell script with custom name passing [-u vimrc] [-U gvimrc] to vim <del> vimWithRC = {vimExecutable, name ? null, vimrcFile ? null, gvimrcFile ? null}: let rcOption = o: file: stdenv.lib.optionalString (file != null) "-${o} ${file}"; in writeScriptBin (if name == null then "vim" else name) '' #!${stdenv.shell} exec ${vimExecutable} ${rcOption "u" vimrcFile} ${rcOption "U" gvimrcFile} "$@" </del> <ins> vimWithRC = { vimExecutable, gvimExecutable, vimManPages, wrapManual, wrapGui, name ? "vim", vimrcFile ? null, gvimrcFile ? null, vimExecutableName, gvimExecutableName, }: let rcOption = o: file: stdenv.lib.optionalString (file != null) "-${o} ${file}"; vimWrapperScript = writeScriptBin vimExecutableName '' #!${stdenv.shell} exec ${vimExecutable} ${rcOption "u" vimrcFile} ${rcOption "U" gvimrcFile} "$@" </ins> ''; <ins> gvimWrapperScript = writeScriptBin gvimExecutableName '' #!${stdenv.shell} exec ${gvimExecutable} ${rcOption "u" vimrcFile} ${rcOption "U" gvimrcFile} "$@" ''; in buildEnv { inherit name; paths = [ vimWrapperScript ] ++ lib.optional wrapGui gvimWrapperScript ++ lib.optional wrapManual vimManPages ; }; </ins> # add a customize option to a vim derivation makeCustomizable = vim: vim // { <del> customize = { name, vimrcConfig }: vimWithRC { </del> <ins> customize = { name, vimrcConfig, wrapManual ? true, wrapGui ? false, vimExecutableName ? name, gvimExecutableName ? (lib.concatStrings [ "g" name ]), }: vimWithRC { </ins> vimExecutable = "${vim}/bin/vim"; <del> inherit name; </del> <ins> gvimExecutable = "${vim}/bin/gvim"; inherit name wrapManual wrapGui vimExecutableName gvimExecutableName; </ins> vimrcFile = vimrcFile vimrcConfig; <ins> vimManPages = buildEnv { name = "vim-doc"; paths = [ vim ]; pathsToLink = [ "/share/man" ]; }; </ins> }; override = f: makeCustomizable (vim.override f);
Code change:
Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
I believe the tlp module could be made to set for those systemd units
Fixed, thanks for your report!

Related discussion:
text: <ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.15.2"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.15/${name}.tar.xz"; sha256 = "0g71zq6dpqrw2f40wfzdf18fdw41ymr17laqniy2kr622hkxdi8w"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>
Code change:
Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
I believe the tlp module could be made to set for those systemd units
Fixed, thanks for your report!

Related discussion:
text: <ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.16.1"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.16/${name}.tar.xz"; sha256 = "1n708n9ixyy9qrzyv1wf4ybvcclx43ib9ki028wwpvkz6kv8zqlb"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>
Code change:
Hi TLP shows the following in output: Anything to do with it? Thanks. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
I believe the tlp module could be made to set for those systemd units
Fixed, thanks for your report!

Related discussion:
text: {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { <del> name = "vala-0.14.2"; </del> <ins> version = "0.17.2"; name = "vala-${version}"; </ins> src = fetchurl { <del> url = mirror://gnome/sources/vala/0.14/vala-0.14.2.tar.xz; sha256 = "1l5kllw9vpwv24lzv9fp64l3sad46wpxgvsgryrwlrjg91w6jzl0"; </del> <ins> url = "mirror://gnome/sources/vala/0.17/${name}.tar.xz"; sha256 = "09i2s0dwmrk147ind2dx7nq845g12fp6fsjqrphhrr0dbi0zzgh3"; </ins> }; buildNativeInputs = [ yacc flex pkgconfig xz ];