From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Brett Gilio <brettg@gnu.org>
Cc: 39695@debbugs.gnu.org
Subject: [bug#39695] [PATCH] [WIP] gnu: mono: Update to 6.8.0.105.
Date: Sun, 26 Jul 2020 12:21:49 +0200 [thread overview]
Message-ID: <875zaamv9e.fsf@ambrevar.xyz> (raw)
In-Reply-To: <878sf7pd73.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Brett Gilio <brettg@gnu.org> writes:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Hi Brett!
>>
>> Brett Gilio <brettg@gnu.org> writes:
>>
>>> Whew! Somebody finally got to it! I tried many times to get mono in a
>>> better shape for Guix, but failed! :) As there are a considerable number
>>> of changes here, would you mind giving a short synopsis of what still
>>> needs to be made before we either reroll a revision or get a final
>>> draft?
>>
>> What still needs to be made? Beside fixing the tests, the patch I've
>> sent seems to have Mono 5 and 6 working.
>>
>> Final draft of what? Sorry, I feel that I'm missing some context :)
>>
>> If your question is about the Mono ecosystem, there is a lot of work
>> left to do. We need a bootstrapped msbuild (the build tool for Mono),
>> and then ideally we would have a mono-build-system. I can detail this
>> if you want to, let me know.
>>
>> Cheers!
>
> Sorry, I wrote this email last night when I was rather tired. I meant to
> say what work still needs to be done on the patch before we commit it.
Nothing essential, the patch can be merged as is, I believe.
> If our ultimate goal is to get .NET Core (with .NET 5 approaching to
> replace .NET Core and .NET Framework, and eventually Mono as well) we
> should maybe invest time into a general .NET build system. I'm not sure.
Absolutely. The investment is significant ;) Maybe the first step
would be to gather a team of volunteers. This is very low priority for
me personally (I don't even know C#). Maybe posting about this on the
mailing list and other social media could be a good start.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-07-26 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 16:23 [bug#39695] [PATCH] [WIP] gnu: mono: Update to 6.8.0.105 Pierre Neidhardt
[not found] ` <handler.39695.B.158221582716665.ack@debbugs.gnu.org>
2020-02-20 16:46 ` [bug#39695] Acknowledgement ([PATCH] [WIP] gnu: mono: Update to 6.8.0.105.) Pierre Neidhardt
2020-07-25 1:56 ` [bug#39695] [PATCH] [WIP] gnu: mono: Update to 6.8.0.105 Brett Gilio
2020-07-25 6:14 ` Pierre Neidhardt
2020-07-25 20:11 ` Brett Gilio
2020-07-26 10:21 ` Pierre Neidhardt [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zaamv9e.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=39695@debbugs.gnu.org \
--cc=brettg@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).