unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: Adam Van Ymeren <adam@vany.ca>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Mono and .NET Core
Date: Wed, 24 Oct 2018 12:41:58 -0500	[thread overview]
Message-ID: <875zxrnswp.fsf@posteo.net> (raw)
In-Reply-To: <96065BAD-4D2B-481A-8629-43E60B68D424@vany.ca>


Adam Van Ymeren writes:

> 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’.


From what I see, coreclr https://github.com/dotnet/coreclr/ now uses a
build.sh script. Is it wise to simply use this in the package definition
to build it (I suspect not), or should the build system be configured
from scratch?

  reply	other threads:[~2018-10-24 17: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
2018-10-24 17:41     ` Brett Gilio [this message]
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

  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=875zxrnswp.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=adam@vany.ca \
    --cc=guix-devel@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).