Packaging/Tutorial: Difference between revisions

Line 8:

<li>Detect package building category. It may be something simple, that ~~requres~~ <code>gcc</code> and <code>make</code> only, or it may be a python library, or it may be a python application, or it may be [https://nixos.org/nixpkgs/manual/#chap-language-support any other LANGUAGE library/application], or it may be Qt applications, or it may be a Gnome application, or it does uses Mono/wine under a hood, or it vendors it's dependencies, or it is closed source/binary redistributable, or it uses CMake/any other alternative build tool, or it actually is a compiler, ... There are lots of such build categories, and it often isn't reflected at hierarchy level in Nixpkgs source tree.</li>

<li>Detect package building category. It may be something simple, that requires <code>gcc</code> and <code>make</code> only, or it may be a python library, or it may be a python application, or it may be [https://nixos.org/nixpkgs/manual/#chap-language-support any other LANGUAGE library/application], or it may be Qt applications, or it may be a Gnome application, or it does uses Mono/wine under a hood, or it vendors it's dependencies, or it is closed source/binary redistributable, or it uses CMake/any other alternative build tool, or it actually is a compiler, ... There are lots of such build categories, and it often isn't reflected at hierarchy level in Nixpkgs source tree.</li>

<li>Try <code>grep</code>ping for building category keywords in Nixpkgs source. Find some example packages, review them and copy one of them as a new expression for your package. Too bad if you didn't find anything, then you should read Nix Pills first and skim through several package expressions in Nixpkgs source to be able to write own one.</li>

<li>Build it without changes, just to test it builds</li>

@@ Line 8: / Line 8: @@
 <ol style="list-style-type: decimal;">
-<li><p>Detect package building category. It may be something simple, that requres <code>gcc</code> and <code>make</code> only, or it may be a python library, or it may be a python application, or it may be [https://nixos.org/nixpkgs/manual/#chap-language-support any other LANGUAGE library/application], or it may be Qt applications, or it may be a Gnome application, or it does uses Mono/wine under a hood, or it vendors it's dependencies, or it is closed source/binary redistributable, or it uses CMake/any other alternative build tool, or it actually is a compiler, ... There are lots of such build categories, and it often isn't reflected at hierarchy level in Nixpkgs source tree.</p></li>
+<li><p>Detect package building category. It may be something simple, that requires <code>gcc</code> and <code>make</code> only, or it may be a python library, or it may be a python application, or it may be [https://nixos.org/nixpkgs/manual/#chap-language-support any other LANGUAGE library/application], or it may be Qt applications, or it may be a Gnome application, or it does uses Mono/wine under a hood, or it vendors it's dependencies, or it is closed source/binary redistributable, or it uses CMake/any other alternative build tool, or it actually is a compiler, ... There are lots of such build categories, and it often isn't reflected at hierarchy level in Nixpkgs source tree.</p></li>
 <li><p>Try <code>grep</code>ping for building category keywords in Nixpkgs source. Find some example packages, review them and copy one of them as a new expression for your package. Too bad if you didn't find anything, then you should read Nix Pills first and skim through several package expressions in Nixpkgs source to be able to write own one.</p></li>
 <li><p>Build it without changes, just to test it builds</p></li>