On Mon, 2023-08-07 at 10:04 +0200, Alexander Kanavin wrote: > On Sun, 6 Aug 2023 at 23:14, Charles-Antoine Couret via > lists.openembedded.org > <[email protected]> wrote: > > documentation/ref-manual/variables.rst | 14 ++++++++ > > meta/classes-recipe/image.bbclass | 30 +++++++++++++++++ > > meta/classes-recipe/image_types.bbclass | 43 ++++++++++++++++++++----- > > This does need tests and examples. You can grep the poky tree for > places where related variables are used, and see if you can expand > those places to include the mechanism. Please include an explanation > or a demonstration for why existing facilities are not good enough. > > Documentation updates go to yocto-docs mailing lists.
Alex is right about this needing tests but there is a deeper issue with this around naming. "MAXSIZE" could easily be interpreted as some kind of upper limit on the filesystem size above which you'd get an error. In reality, it is an override on the overall partition size to a specific value, which isn't a maximum at all. I understand the need to differentiate it with IMAGE_ROOTFS_SIZE but effectively they are the same thing or very closely related. I think the naming needs a lot more thought. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185731): https://lists.openembedded.org/g/openembedded-core/message/185731 Mute This Topic: https://lists.openembedded.org/mt/100588377/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
