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<[email protected]>
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
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[email protected]"
