migration-guides: Add coverage of addpylib directive

To complement what I am adding to the BitBake reference manual, add a
section in the 4.2 migration guide, a reference in the structure section
of the reference manual (where we talk about meta/lib) and adjust the
release notes item to be a little more concise.

(From yocto-docs rev: 0903e82a9da263c6d64aead03407eb377eb5bbfe)

Signed-off-by: Paul Eggleton <bluelightning@bluelightning.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 2 insertions, 6 deletions

diff --git a/documentation/migration-guides/release-notes-4.2.rst b/documentation/migration-guides/release-notes-4.2.rst
index 4cf1974d4f..a3e821cb4b 100644
--- a/documentation/migration-guides/release-notes-4.2.rst
+++ b/documentation/migration-guides/release-notes-4.2.rst
@@ -11,12 +11,8 @@ New Features / Enhancements in 4.2
    :term:`buildtools` tarball.
 
 -  BitBake in this release now supports a new ``addpylib`` directive to enable
-   Python libraries within layers.
-
-   This directive should be added to your layer configuration
-   as in the below example from ``meta/conf/layer.conf``::
-
-      addpylib ${LAYERDIR}/lib oe
+   Python libraries within layers. For more information,
+   see :ref:`bitbake-user-manual/bitbake-user-manual-metadata:extending python library code`.
 
 -  BitBake has seen multiple internal changes that may impact
    memory and disk usage as well as parsing time, in particular: