From: Adam Van Ymeren <adam@vany.ca>
To: ludo@gnu.org, Brett Gilio <brettg@posteo.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Mono and .NET Core
Date: Wed, 24 Oct 2018 22:42:23 +0900 [thread overview]
Message-ID: <96065BAD-4D2B-481A-8629-43E60B68D424@vany.ca> (raw)
In-Reply-To: <87in1r4hum.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
I tried to package .NET Core a while ago but didn't produce anything useful. Their GNU/Linux story was rapidly changing at the time.
.NET Core was a pain to package partly because it bootstraps from a binary version of .NET Core similar to Rust. Although it may be possible to bootstrap via Mono I didn't try it and it's definitely not an upstream supported route ;).
Personally I ended up with just sticking to Mono for my C# needs as I found .NET Core didn't integrate as nicely into the GNU/Linux ecosystem.
That being said it would certainly be nice to have packages for it in Guix.
On October 24, 2018 10:03:29 PM GMT+09:00, ludo@gnu.org wrote:
>Hello!
>
>Brett Gilio <brettg@posteo.net> skribis:
>
>> Two questions here.
>>
>> 1) Has anybody already started taking to try and upgrade Mono to
>latest?
>> If not, I will give it a go.
>>
>> 2) Have we started any packaging on .NET Core, would like to know to
>> prevent redundancy in work.
>
>AFAIK nobody worked in this area yet, so you’ll probably have the
>privilege to be a pioneer! :-)
>
>Mono was added by janneke (Cc’d), who might have something to add?
>
>Ludo’.
[-- Attachment #2: Type: text/html, Size: 1571 bytes --]
next prev parent reply other threads:[~2018-10-24 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 4:26 Mono and .NET Core Brett Gilio
2018-10-24 13:03 ` Ludovic Courtès
2018-10-24 13:42 ` Adam Van Ymeren [this message]
2018-10-24 17:41 ` Brett Gilio
2018-10-24 16:38 ` Jan Nieuwenhuizen
2018-10-24 13:04 ` Ludovic Courtès
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=96065BAD-4D2B-481A-8629-43E60B68D424@vany.ca \
--to=adam@vany.ca \
--cc=brettg@posteo.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.