From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Angelo Compagnucci <angelo@amarulasolutions.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/mono: allow to select which folders to install to target
Date: Tue, 1 Nov 2022 18:42:00 +0100 [thread overview]
Message-ID: <20221101174200.GJ2992523@scaer> (raw)
In-Reply-To: <CA+_SqVZMnZvF2-n4HvrUUg1=k-VT4QBZGNAHZpoGM86y37fyuw@mail.gmail.com>
Angelo, All,
On 2022-11-01 10:19 +0100, Angelo Compagnucci spake thusly:
[--SNIP--]
> My two cents. Historically, the mono configure was offering some
> options to enable only some versions of the API which was lately
> removed
> So, removing older compatibility API folders should be perfectly
> fine.
Thanks for the confirmation! :-)
My understanding, though, would be that we may need more than one such
versionned API. For example, I would (hypothetically!) develope my app
agaings current version, say 4.8-api, so I am using APIs from that
version. Then I update to a newer mono, and I start using the new APIs,
e.g. 5.3-api, in the new parts of my app, but the existing parts are
still using 4.8-api, so I need both.
Is that sensible, or did I mis-understood?
If correct, then we need to be able to select more than one versioned
API.
> We cannot remove the Global Assembly Cache (GAC).
So, we an' rely on it being listed by the user; we must explicitly
install it.
MONO_INSTALL_DIRS = \
gac \
$(fitler-out gac,$(call qstrip,$(BR2_PACKAGE_MONO_API_DIRS)))
$(foreach dir,$(MONO_INSTALL_DIRS),copy the $(d) dir)
> For the rest, it would be nice if Giulio could do some testing (I can
> try it too) to understand at what extent we can remove any other
> folder.
That would be awesome, thanks!
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
next prev parent reply other threads:[~2022-11-01 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 23:46 [Buildroot] [PATCH] package/mono: allow to select which folders to install to target Giulio Benetti
2022-10-19 16:16 ` Angelo Compagnucci
2022-10-31 12:25 ` Thomas Petazzoni via buildroot
2022-10-31 12:54 ` Yann E. MORIN
2022-11-01 2:27 ` Giulio Benetti
2022-11-01 8:32 ` Yann E. MORIN
2022-11-01 9:19 ` Angelo Compagnucci
2022-11-01 17:42 ` Yann E. MORIN [this message]
2022-11-01 20:30 ` Angelo Compagnucci
2022-11-01 18:17 ` Giulio Benetti
2022-11-01 16:44 ` Giulio Benetti
2022-11-01 2:19 ` Giulio Benetti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221101174200.GJ2992523@scaer \
--to=yann.morin.1998@free.fr \
--cc=angelo.compagnucci@gmail.com \
--cc=angelo@amarulasolutions.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox