···

       
661
       
661
       
 
       
</section>

     

       
662
       
662
       
 
       


     

       
663
       
663
       
 
       
<section xml:id="sec-patches"><title>Patches</title>

     

       
664
       
664
       
-
       
  <para>Only patches that are unique to <literal>nixpkgs</literal> should be

     

       
665
       
665
       
-
       
    included in <literal>nixpkgs</literal> source.</para>

     

       
666
       
664
       
 
       
  <para>Patches available online should be retrieved using

     

       
667
       
665
       
 
       
    <literal>fetchpatch</literal>.</para>

     

       
668
       
666
       
 
       
  <para>

     
···

       
676
       
674
       
 
       
];

     

       
677
       
675
       
 
       
</programlisting>

     

       
678
       
676
       
 
       
  </para>

     

       
677
       
677
       
+
       
  <para>Otherwise, you can add a <literal>.patch</literal> file to the

     

       
678
       
678
       
+
       
  <literal>nixpkgs</literal> repository. In the interest of keeping our

     

       
679
       
679
       
+
       
  maintenance burden to a minimum, only patches that are unique

     

       
680
       
680
       
+
       
  to <literal>nixpkgs</literal> should be added in this way.</para>

     

       
681
       
681
       
+
       
<para><programlisting>

     

       
682
       
682
       
+
       
patches = [ ./0001-changes.patch ];

     

       
683
       
683
       
+
       
</programlisting></para>

     

       
684
       
684
       
+
       
  <para>If you do need to do create this sort of patch file,

     

       
685
       
685
       
+
       
  one way to do so is with git:

     

       
686
       
686
       
+
       
  <orderedlist>

     

       
687
       
687
       
+
       
    <listitem><para>Move to the root directory of the source code

     

       
688
       
688
       
+
       
    you're patching.<screen>

     

       
689
       
689
       
+
       
$ cd the/program/source</screen></para></listitem>

     

       
690
       
690
       
+
       
    <listitem><para>If a git repository is not already present,

     

       
691
       
691
       
+
       
    create one and stage all of the source files.<screen>

     

       
692
       
692
       
+
       
$ git init

     

       
693
       
693
       
+
       
$ git add .</screen></para></listitem>

     

       
694
       
694
       
+
       
    <listitem><para>Edit some files to make whatever changes need

     

       
695
       
695
       
+
       
    to be included in the patch.</para></listitem>

     

       
696
       
696
       
+
       
    <listitem><para>Use git to create a diff, and pipe the output

     

       
697
       
697
       
+
       
    to a patch file:<screen>

     

       
698
       
698
       
+
       
$ git diff > nixpkgs/pkgs/the/package/0001-changes.patch</screen>

     

       
699
       
699
       
+
       
    </para></listitem>

     

       
700
       
700
       
+
       
  </orderedlist></para>

     

       
679
       
701
       
 
       
</section>

     

       
702
       
702
       
+
       


     

       
680
       
703
       
 
       
</chapter>