diff options
Diffstat (limited to 'documentation/migration-guides/migration-general.rst')
| -rw-r--r-- | documentation/migration-guides/migration-general.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/migration-guides/migration-general.rst b/documentation/migration-guides/migration-general.rst index c350a4df97..c3b8a785db 100644 --- a/documentation/migration-guides/migration-general.rst +++ b/documentation/migration-guides/migration-general.rst | |||
| @@ -81,11 +81,11 @@ any new Yocto Project release. | |||
| 81 | the migration (e.g. added/removed packages, added/removed files, size | 81 | the migration (e.g. added/removed packages, added/removed files, size |
| 82 | changes etc.). To do this, follow these steps: | 82 | changes etc.). To do this, follow these steps: |
| 83 | 83 | ||
| 84 | 1. Enable :ref:`buildhistory <ref-classes-buildhistory>` before the migration | 84 | #. Enable :ref:`buildhistory <ref-classes-buildhistory>` before the migration |
| 85 | 85 | ||
| 86 | 2. Run a pre-migration build | 86 | #. Run a pre-migration build |
| 87 | 87 | ||
| 88 | 3. Capture the :ref:`buildhistory <ref-classes-buildhistory>` output (as | 88 | #. Capture the :ref:`buildhistory <ref-classes-buildhistory>` output (as |
| 89 | specified by :term:`BUILDHISTORY_DIR`) and ensure it is preserved for | 89 | specified by :term:`BUILDHISTORY_DIR`) and ensure it is preserved for |
| 90 | subsequent builds. How you would do this depends on how you are running | 90 | subsequent builds. How you would do this depends on how you are running |
| 91 | your builds - if you are doing this all on one workstation in the same | 91 | your builds - if you are doing this all on one workstation in the same |
| @@ -93,15 +93,15 @@ any new Yocto Project release. | |||
| 93 | deleting the :ref:`buildhistory <ref-classes-buildhistory>` output | 93 | deleting the :ref:`buildhistory <ref-classes-buildhistory>` output |
| 94 | directory. For builds in a pipeline it may be more complicated. | 94 | directory. For builds in a pipeline it may be more complicated. |
| 95 | 95 | ||
| 96 | 4. Set a tag in the :ref:`buildhistory <ref-classes-buildhistory>` output (which is a git repository) before | 96 | #. Set a tag in the :ref:`buildhistory <ref-classes-buildhistory>` output (which is a git repository) before |
| 97 | migration, to make the commit from the pre-migration build easy to find | 97 | migration, to make the commit from the pre-migration build easy to find |
| 98 | as you may end up running multiple builds during the migration. | 98 | as you may end up running multiple builds during the migration. |
| 99 | 99 | ||
| 100 | 5. Perform the migration | 100 | #. Perform the migration |
| 101 | 101 | ||
| 102 | 6. Run a build | 102 | #. Run a build |
| 103 | 103 | ||
| 104 | 7. Check the output changes between the previously set tag and HEAD in the | 104 | #. Check the output changes between the previously set tag and HEAD in the |
| 105 | :ref:`buildhistory <ref-classes-buildhistory>` output using ``git diff`` or ``buildhistory-diff``. | 105 | :ref:`buildhistory <ref-classes-buildhistory>` output using ``git diff`` or ``buildhistory-diff``. |
| 106 | 106 | ||
| 107 | For more information on using :ref:`buildhistory <ref-classes-buildhistory>`, see | 107 | For more information on using :ref:`buildhistory <ref-classes-buildhistory>`, see |