about summary refs log tree commit diff
path: root/doc/languages-frameworks
AgeCommit message (Collapse)AuthorFilesLines
2023-11-20texlive: document simpler way to build custom packagesVincenzo Mantova1-17/+34
2023-11-16Merge pull request #258184 from mdarocha/dotnet-fixesWeijia Wang1-1/+3
buildDotnetModule small improvements
2023-11-16buildNpmPackage: allow passing npmDepshappysalada1-0/+1
2023-11-15Merge pull request #265053 from fricklerhandwerk/fix-dhallpkgs-docValentin Gagarin1-1/+1
2023-11-14buildGoModule: deprecate vendorSha256 attributeAaron Jheng1-1/+1
2023-11-12Merge pull request #267087 from tufteddeer/patch-1Lily Foster1-1/+1
docs/javascript/introduction: fix GitHub search link
2023-11-12docs/javascript/introduction: fix GitHub search linkFabian1-1/+1
2023-11-12Update doc/languages-frameworks/rust.section.mdAdam Joseph1-0/+1
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
2023-11-11rust: add tutorial on git-bisecting rustcAdam Joseph1-0/+64
This commits adds to the manual a tutorial showing how to troubleshoot breakage caused by a rustc upgrade in *downstream* packages.
2023-11-11treewide: fix redirected and broken URLsAnthony Roussel1-1/+1
Using the script in maintainers/scripts/update-redirected-urls.sh
2023-11-10Merge pull request #256816 from Artturin/pythondocpython3packagesArtturi1-7/+7
2023-11-09doc: avoid 'simply' (#266434)Arnout Engelen10-19/+19
While the word 'simply' is usually added to encourage readers, it often has the opposite effect and may even appear condescending, especially when the reader runs into trouble trying to apply the suggestions from the documentation. It is almost always an improvement to simply drop the word from the sentence. (there are more possible improvements like this, we can apply those in separate PRs)
2023-11-09buildNpmPackage: make nodejs overridable (#265171)Yt1-0/+1
* buildNpmPackage: allow nodejs to be passed as argument * Update doc/languages-frameworks/javascript.section.md Co-authored-by: Lily Foster <lily@lily.flowers> --------- Co-authored-by: Lily Foster <lily@lily.flowers>
2023-11-09doc/languages-frameworks/python: update recommended commit messagenatsukium1-1/+3
2023-11-09doc/languages-frameworks/python: switch pythonPackages to python3Packagesnatsukium1-12/+12
Replaced with python3Packages except for the following to avoid misuse of pythonPackages 1. which we need for the explanation 2. which are replaced by python3Packages as variables
2023-11-09doc/languages-frameworks/python: update interpreters versionnatsukium1-4/+6
2023-11-08Merge pull request #265764 from amjoseph-nixpkgs/pr/pythonForBuildArtturi1-2/+2
2023-11-07texlive: document new texlive.withPackages interface (#265658)Vincenzo Mantova1-0/+40
2023-11-05treewide: change pythonForBuild to pythonOnBuildForHostAdam Joseph1-2/+2
2023-11-02fixup note on dhall-to-nixpkgs exampleValentin Gagarin1-1/+1
2023-11-01Merge pull request #250805 from xworld21/texlive-buildenv-minimalDmitry Kalinkin1-0/+18
texlive: overrideTeXConfig/withPackages
2023-10-29luarocks-packages-update: init (#262156)Matthieu Coudron1-3/+3
* luarocks-packages-updater: init Goal is to make it possible to maintain out-of-tree luarocks packages without needing to clone nixpkgs. maintainers/scripts/update-luarocks-packages gets renamed to pkgs/development/lua-modules/updater/updater.py Once merged you can run for instance nix run nixpkgs#luarocks-packages-updater -- -i contrib/luarocks-packages.csv -o contrib/generated-packages.nix I also set the parallelism (--proc) to 1 by default else luarocks fails because of https://github.com/luarocks/luarocks/issues/1540 * Update maintainers/scripts/pluginupdate.py Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com> --------- Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
2023-10-26Merge pull request #258595 from fricklerhandwerk/doc-emscriptenValentin Gagarin1-156/+141
Emscripten docs: reword and remove mention of `nix-env`
2023-10-24doc: use lib.fakeHash with buildGoModule to get vendorHashStel Abrego1-1/+1
lib.fakeSha256 results in `error: hash <fake_hash> does not include a type, nor is the type otherwise known from context`.
2023-10-21Merge pull request #231483 from hacker1024/feature/flutter-on-dartMaciej Krüger1-3/+4
buildFlutterApplication: Wrap buildDartApplication
2023-10-21doc/python: mention python313Martin Weinelt1-0/+1
2023-10-21buildDartApplication: Use package override mechanism from ↵hacker10241-3/+4
buildFlutterApplication This allows Dart applications to benefit from the package override system, which is useful for things like FFI dependencies.
2023-10-09link to documentation on IFD in the Nix manualValentin Gagarin1-1/+1
2023-10-08Merge pull request #258384 from doronbehar/buildNpmPackage-makeWrapperArgsDoron Behar1-1/+15
buildNpmPackage: support makeWrapperArgs
2023-10-07texlive: document new texlive.pkgs attributeVincenzo Mantova1-0/+18
2023-10-07buildNpmPackage: support makeWrapperArgsDoron Behar1-0/+1
2023-10-07docs/javascript/buildNpmPackage: Document fetchNpmDepsDoron Behar1-1/+10
Co-authored-by: Lily Foster <lily@lily.flowers>
2023-10-07docs/javascript/buildNpmPackage: Document bin, man and npm pack behaviorDoron Behar1-0/+4
2023-10-04Merge master into haskell-updatesgithub-actions[bot]1-5/+6
2023-10-03emscripten docs: reformat examples to use admonitionValentin Gagarin1-113/+128
that way the examples will also appear in the appendix Co-authored by: Henrik Karlsson <i97henka@gmail.com>
2023-10-03emscripten docs: reword introductionValentin Gagarin1-40/+10
in particular, remove mention of `nix-env` Co-authored by: Henrik Karlsson <i97henka@gmail.com>
2023-10-01vimPluginsUpdater: initMatthieu Coudron1-5/+6
The nixpkgs documentation mentions how to update out of tree plugins but one problem is that it requires a nixpkgs clone. This makes it more convenient. I've had the need to generate vim plugins and lua overlays for other projects unrelated to nix and this will make updates easier (aka just run `nix run nixpkgs#vimPluginsUpdater -- --proc=1` or with the legacy commands: `nix-shell -p vimPluginsUpdater --run vim-plugins-updater`. I added an optional "nixpkgs" argument to command line parser, which is the path towards a nixpkgs checkout. By default the current folder. update-luarocks-packages: format with black
2023-09-30buildDotnetModule: make docs more clear on how to generate nugetDeps for the ↵mdarocha1-1/+3
first time
2023-09-29Merge master into haskell-updatesgithub-actions[bot]3-4/+4
2023-09-28treewide: Fix typosPeder Bergebakken Sundt3-4/+4
2023-09-28Merge master into haskell-updatesgithub-actions[bot]1-1/+1
2023-09-27vimUtils: buildVimPluginFrom2Nix renamed to buildVimPluginMatthieu Coudron1-1/+1
the `from2Nix` suffix is a legacy from vim2nix but we dont use that anymore. It makes the name of the function unusual and long.
2023-09-26Merge master into haskell-updatesgithub-actions[bot]2-6/+6
2023-09-25use `nix-shell -p` for `dhall-to-nixpkgs` exampleValentin Gagarin1-5/+6
2023-09-25Merge pull request #254309 from pbsds/flit-pruneFrederik Rietdijk1-1/+0
python3Packages.flitBuildHook: remove
2023-09-25Merge master into haskell-updatesgithub-actions[bot]1-78/+78
2023-09-24nixpkgs manual: doc python: add hyperlinks to Python section (#252156)Alejandro Sánchez Medina1-78/+78
* nixpkgs manual: doc python: add hyperlinks to Python section Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-09-23doc/python: use python3Packages instead of python3.pkgsArtturin1-7/+7
Allows splicing to work correctly from issue 211340 >> 3: Discourage using package sets like python3.pkgs "directly" > I think about 8 years ago I introduced this and it has been a clear mistake. Since then this pattern was copied throughout. We should indeed go to pythonPackages and also move the helpers such as buildEnv and withPackages into the package set, like haskell already had before. - FRidh
2023-09-22python3Packages.flitBuildHook: removePeder Bergebakken Sundt1-1/+0
2023-09-21Merge master into haskell-updatesgithub-actions[bot]1-0/+4
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-15 09:25:50 +0000