Re: [Buildroot] [PATCH] package/mono: allow to select which folders to install to target

["Yann E. MORIN" <yann.morin.1998@free.fr>]

Giulio, All,

On 2022-11-01 03:27 +0100, Giulio Benetti spake thusly:
> On 31/10/22 13:54, Yann E. MORIN wrote:
> >On 2022-10-31 13:25 +0100, Thomas Petazzoni via buildroot spake thusly:
> >>On Wed, 19 Oct 2022 01:46:17 +0200
> >>Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> >>>At the moment all APIs folders are copied to target increasing the size of
> >>>rootfs of ~190MB. Allow to select which API folders we want to copy to
> >>>target to shrink rootfs down.
> >>>
> >>>Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> >>Practically speaking, could you describe which folders are needed in a
> >>typical scenario you've had?
> >Yes, can you provide a rationale for when only a subset of APIs is
> >needed?
> I've answered on previous e-mail. I've realized only now that I could
> answer to your e-mail for both.

Hey, what you answered Thomas is not a rationale, it is an example. ;-)
A rationale is "an explanation of controlling principles of opinion,
belief, practice, or phenomena", or "an underlying reason". [0]

As a rationale, I would have expected something that explains the reason
why there are so many directories, and so why, under some circumstances,
we can get rid of them (or not). It needs not be too long, but just
provide an overview. For example, here is a totally made up blurb:

    mono provides support for a lot of legacy APIs for backward
    compatibility for existing applications, way back from the first
    stable API, 2.0 and up to the current version. The set of APIs are
    split in two categories: version-based APIs, and the rest (gac, the
    FooBar set of common Baz; monodoc, which renders documentation while
    riding a unicycle...).

    For a custom application, the set of required versioned APIs is
    limited; most often only the latest or the very few latest are
    needed. Only gac is always required, and monodoc is never used on
    the target as we never render the documentation there.

[0] https://www.merriam-webster.com/dictionary/rationale

[--SNIP--]
> >>Should we instead have a single string option
> >>BR2_PACKAGE_MONO_INSTALL_LIB_DIRS, which is empty by default. When
> >>empty, it means all folders are installed. Otherwise, only the
> >>specified folders are installed.
> >Agreed. I expect that having no API level installed would yield a
> >non-working system, so:
> >     config BR2_PACKAGE_MONO_API_VERSIONS
> >         string "API versions to install"
> >         help
> >           Keep empty to install all.
> Ok, I go with that then!

ACK.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot