Re: New Mono/.Net ports team?
Awesome guys, it sounds like everyone is on the same page. I have transposed a snippet from Romain into this thread: > If it can help, I have been running MonoDevelop on top of GitHub master > branch with no patch for some times. It currently does not build on my > machine (errors related to FSharp, FSharp failing ot build with Mono > 4.4, so maybe everything is linked). > > The configure script / makefile takes care of these submodules, so > updating MonoDevelop when I used this was really as simple as `git pull > && gmake && gmake run` Interesting, that may be the slant I was missing. I couldn't get the submodules in the external folder to load, perhaps the trick was to call the configure file from the ports makefile target. I was attempting to use the the port variables in example 5.4 here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#makefile-master_sites-github-ex2 Arron, section 5.4.3 is the info you will need to convert the ports Makefile over to github. Thanks, Romain, your input is greatly appreciated. I will attempt to build from head again and perhaps the Rosyln tag. I'll clean my notes up and email them tonight. Russ On Sun, Jun 19, 2016 at 11:40 AM, Carsten Larsen wrote: > 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 ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: New Mono/.Net ports team?
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 ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: New Mono/.Net ports team?
On Sat, Jun 18, 2016 at 11:01 PM, Russell Haley wrote: > Okay, so there has been more than one person that has expressed > interest in playing in this space, I'll bite. > > I propose the following: > 1) I'll put my notes together and get monodevelop running from github. > There are also some binary installations that I think we might be able > to get rid of. > 2) Some one starts going over the porters handbook and lookg at > creating a new portcreate a new port pointing to github > 3) Someone gets a.Net Core build running agian and then we create a > port for that, even if it includes a binary installation. > > 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'm willing to throw 8 hours a month at this. Probably more to get it > started. > > The one person who is notably absent from this conversation is the > only one among us with any commit rights: Mr. Romain Tartière. > > Mr. Tartiere, are you willing to help us out? > > Cheers, > > Russ > Thanks Russ. I am interested in helping out. I will take a look at the porters handbook. Aaron ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
New Mono/.Net ports team?
Okay, so there has been more than one person that has expressed interest in playing in this space, I'll bite. I propose the following: 1) I'll put my notes together and get monodevelop running from github. There are also some binary installations that I think we might be able to get rid of. 2) Some one starts going over the porters handbook and lookg at creating a new portcreate a new port pointing to github 3) Someone gets a.Net Core build running agian and then we create a port for that, even if it includes a binary installation. 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'm willing to throw 8 hours a month at this. Probably more to get it started. The one person who is notably absent from this conversation is the only one among us with any commit rights: Mr. Romain Tartière. Mr. Tartiere, are you willing to help us out? Cheers, Russ ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
