| OLD | NEW |
| 1 naclports - Ports of open source software to Native Client | 1 naclports - Ports of open source software to Native Client |
| 2 ========================================================== | 2 ========================================================== |
| 3 | 3 |
| 4 naclports is collection of open source libraries and applications that have | 4 naclports is collection of open source libraries and applications that have |
| 5 been ported to Native Client, along with set to tools for building and | 5 been ported to Native Client, along with set to tools for building and |
| 6 maintaining them. | 6 maintaining them. |
| 7 | 7 |
| 8 Packages can be built from source or prebuilt binaries packages can be | 8 Packages can be built from source or prebuilt binaries packages can be |
| 9 downloaded from the continuous build system. | 9 downloaded from the continuous build system. |
| 10 | 10 |
| (...skipping 212 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 223 ``out/build/<pkg_name>``. A new git repository is then created in this | 223 ``out/build/<pkg_name>``. A new git repository is then created in this |
| 224 folder with the original archive contents on a branch called ``upstream``. The | 224 folder with the original archive contents on a branch called ``upstream``. The |
| 225 optional ``nacl.patch`` file is then applied on the ``master`` branch. This | 225 optional ``nacl.patch`` file is then applied on the ``master`` branch. This |
| 226 means that at any given time you can see the changes from upstream using ``git | 226 means that at any given time you can see the changes from upstream using ``git |
| 227 diff upstream``. | 227 diff upstream``. |
| 228 | 228 |
| 229 To make changes to a package's patch file the recommended workflow is: | 229 To make changes to a package's patch file the recommended workflow is: |
| 230 | 230 |
| 231 1. Directly modify the sources in ``out/build/<pkg_name>``. | 231 1. Directly modify the sources in ``out/build/<pkg_name>``. |
| 232 2. Build the package and verify the changes. | 232 2. Build the package and verify the changes. |
| 233 3. Use ``naclpors updatepatch <pkg_name>`` to (re)generate the patch file. | 233 3. Use ``naclports updatepatch <pkg_name>`` to (re)generate the patch file. |
| 234 | 234 |
| 235 Whenever the upstream archive or patch file changes and you try to build the | 235 Whenever the upstream archive or patch file changes and you try to build the |
| 236 package you will be prompted to remove the existing repository and start a new | 236 package you will be prompted to remove the existing repository and start a new |
| 237 one. This is to avoid deleting a repository that might contain unsaved changed. | 237 one. This is to avoid deleting a repository that might contain unsaved changed. |
| 238 | 238 |
| 239 Happy porting! | 239 Happy porting! |
| OLD | NEW |