From owner-freebsd-mono@freebsd.org Sun Jun 19 18:40:21 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05FE4A7AE27 for ; Sun, 19 Jun 2016 18:40:21 +0000 (UTC) (envelope-from cs@innolan.dk) Received: from avril.innolan.net (ntp2.innolan.net [90.184.222.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF9D61A2C; Sun, 19 Jun 2016 18:40:20 +0000 (UTC) (envelope-from cs@innolan.dk) Received: from [192.168.10.60] (unknown [192.168.222.119]) by avril.innolan.net (Postfix) with ESMTP id 3583461F8D2; Sun, 19 Jun 2016 20:40:11 +0200 (CEST) Subject: Re: New Mono/.Net ports team? To: Russell Haley , Freebsd-mono References: Cc: Mathieu Prevot , romain@freebsd.org From: Carsten Larsen Message-ID: <5766E70A.7030400@innolan.dk> Date: Sun, 19 Jun 2016 20:40:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2016 18:40:21 -0000 Hi I have been working with .NET for more than 10 years and with FreeBSD for around 5. Neither of them are my main profession anymore but I still enjoy working with both of them. I would also be willing to help leveraging the platform on FreeBSD. On Sun, Jun 19, 2016 at 06:01, Russell Haley wrote: > 2) Some one starts going over the porters handbook and lookg at > creating a new portcreate a new port pointing to github I recently went through the process by submitting net/ntpa. You could take at the port source. I found xbuild to be the best solution. I also found a bit of inspiration by looking at the other .NET ports in the ports tree, notably emby-server. Browsing on github gives an idea of how other ports are installed. Look at the Makefile for emby-server f.x: https://github.com/freebsd/freebsd-ports/blob/master/multimedia/emby-server/Makefile > 3) Someone gets a.Net Core build running agian and then we create a > port for that, even if it includes a binary installation. The build scripts for dotnet core looks terrible. I am not sure its worth the effort taking their current state into consideration. Maybe I am wrong but they look like a prof of concept. > > I also think it's important to start getting some .net ports in there > as well, like Pinta and...er... are there any others? I though about porting ADO database providers, especially MySQL Connector and PostgreSQL npgsql. So far I didn't figure out how to do it. I guess they should be installed in GAC as signed and strongly named assemblies. Other components like log4net could also be handy to have in the ports tree. Personally I think NuGet should only be used in a development environment. How about CruiseControl.NET ? Carsten Larsen