Re: lang/mono: testers wanted for 6.8.0.96 update!

2020-01-31 Thread Marcin Cieslak 

On Tue, 21 Jan 2020, Phillip R. Jaenke wrote:


Just go here: https://reviews.freebsd.org/D2330


https://reviews.freebsd.org/D23300

Thanks for picking it up! I have upstreamed some FreeBSD
changes to mono in the past and I am happy this gets
picked up again!

Marcin

smime.p7s
Description: S/MIME Cryptographic Signature

Re: DotNet Core on FreeBSD

2017-09-10 Thread Marcin Cieslak 
On Sun, 10 Sep 2017, Russell Haley wrote:

> Hey guys,
> 
> I am talking to Karel and Tomas at Microsoft's DotNet Core Team about
> putting together a "proposal" for community involvement, which will be
> followed by more information on this list. Most of the talk has been
> me blowing air and being pedantic about nothing (I get excited and
> type alot).

I was tinkering around FreeBSD support when dotnet core was first published.
Stack unwinding for exceptions was very hacky at the time, and there were
some unnecessary discussions about how to implement some FreeBSD sepecific
sysctl's. I got a bit frustrated with that (a whole porting effort is about
coercing Unix to offer part of Win32 APIs).

It was somewhat running on FreeBSD natively back then, haven't checked
recently.

I have also decided not to sign their bad contributor agreement
and some of the sysctl code I decided to put in mono instead :)

Marcin
saper on github

smime.p7s
Description: S/MIME Cryptographic Signature

Re: lang/mono: Update to 4.0.3.19

2015-08-11 Thread Marcin Cieslak 

On Sun, 9 Aug 2015, Kurt Jaeger wrote:

 Hi!
 
  Ok, got that. As Romain is the maintainer of the port, he needs
  to approve PR 201883
 
 Technically, after 14 days oe non-action on a PR, the maintainer is
 seen as timed-out for that PR and anyone can commit. This is almost
 the case with that PR.

We have mono@ mailing list, which is the maintainer. (I'd suggest
moving this thread there).

 There are other issues to consider:
 
 I used
 
 grep -Rl '{PORTSDIR}/lang/mono' *  /tmp/mono

We have USES=mono

The mailing list is full of automated complaints about
failing dependencies. There are also human complaints
that monodevelop is old and/or doesn't work.

Not sure what is the official policy but you can
be maintainer *right now* on behalf of mono@

I also would love some help in getting

https://github.com/mono/mono/pull/1870

committed to mono and getting

https://github.com/mono/mono/pull/1859
https://github.com/mono/mono/pull/1860
https://github.com/mono/mono/pull/1861
https://github.com/mono/mono/pull/1863
https://github.com/mono/mono/pull/1864
https://github.com/mono/mono/pull/1865
https://github.com/mono/mono/pull/1866
https://github.com/mono/mono/pull/1867

backported to 4.0.3

as well as help with how to proceed with

https://github.com/mono/mono/pull/1882

futher - maybe by getting mono working with
system iconv and not the GNU one - see
http://lists.freebsd.org/pipermail/freebsd-ports/2015-July/099675.html

~Marcin


___
freebsd-mono@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to freebsd-mono-unsubscr...@freebsd.org