diff options
author | Antonin Godard <antonin.godard@bootlin.com> | 2024-10-24 10:59:06 +0200 |
---|---|---|
committer | Steve Sakoman <steve@sakoman.com> | 2024-10-30 08:30:00 -0700 |
commit | 53109476046052def3749164b33a3413ed6542f8 (patch) | |
tree | 9d5328d239eee6a3165fa69fd85a67372722e283 | |
parent | cab2c6b225aebdd09b86274b036ff15b862ea02e (diff) | |
download | poky-53109476046052def3749164b33a3413ed6542f8.tar.gz |
ref-manual: faq: add q&a on class appends
Add the suggestion by Richard to the FAQ, with some minor rewordings and
additional punctuations.
Suggested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
(From yocto-docs rev: a030626167905034e24589119453ca6f5fb41cfe)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit 2466a5e7973bf6e724f1cf0b42f838065847d283)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
-rw-r--r-- | documentation/ref-manual/faq.rst | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index bab284bbfd..9e3418e10d 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst | |||
@@ -259,6 +259,25 @@ Within the :term:`Build Directory`, is the ``tmp`` directory. To remove all the | |||
259 | build output yet preserve any source code or downloaded files from | 259 | build output yet preserve any source code or downloaded files from |
260 | previous builds, simply remove the ``tmp`` directory. | 260 | previous builds, simply remove the ``tmp`` directory. |
261 | 261 | ||
262 | Why isn't there a way to append bbclass files like bbappend for recipes? | ||
263 | ------------------------------------------------------------------------ | ||
264 | |||
265 | The Yocto Project has consciously chosen not to implement such functionality. | ||
266 | Class code is designed to be shared and reused, and exposes some level of | ||
267 | configuration to its users. We want to encourage people to share these changes | ||
268 | so we can build the best classes. | ||
269 | |||
270 | If the ``append`` functionality was available for classes, our evidence and | ||
271 | experience suggest that people would create their custom changes in their | ||
272 | layer instead of sharing and discussing the issues and/or limitations they | ||
273 | encountered. This would lead to bizarre class interactions when new layers are | ||
274 | included. We therefore consciously choose to have a natural pressure to share | ||
275 | class code improvements or fixes. | ||
276 | |||
277 | There are also technical considerations like which recipes a class append would | ||
278 | apply to and how that would fit within the layer model. These are complications | ||
279 | we think we can live without! | ||
280 | |||
262 | Customizing generated images | 281 | Customizing generated images |
263 | ============================ | 282 | ============================ |
264 | 283 | ||