Re: Maintaining mono/.net
On Tue, Jun 28, 2016 at 2:43 AM, Baptiste Daroussin wrote: > On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: >> Hello Ports Team, >> >> A couple of us on the freebsd-mono@ mailing list are having a >> discussion on how best to maintain the mono ports/.net ports. One of >> the things that has come up is maintaining the patches for "all this >> stuff". The current paradigm in FreeBSD as I understand it is to use >> the files directory and apply the patches to the port via svn/ports >> tree. However, with the ubiquity of GitHub in opensource, it now seems >> to be feesable to simply create a Github accound to maintain a bunch >> of forked repositories (which is essentially a patched git >> repository!). This makes it easier to create and apply patches and >> gives us the natural path to push things back upstream. In the end, we >> would just pull from the FreeBSD specific repository, which is no >> different than, say, pulling from the mono project directly. >> >> This email is a request for response from anyone on the ports team (or >> FreeBSD general) to give some input as to the acceptability of this >> solution, as well as any "gotchas" we haven't thought of yet. Thanks >> in advance! >> > There are absolutely nothing against this. Actually some ports were already > doing that before the github era :D > > The only difficulty the history told us is : when active people get less > active > for various reasons you need to make sure enough people continues to get > access > to the said repo. > > Tracking upstream updates because more complicated for people not in the team > (we already saw in the past ports stucked for more than 5/6 years actions > being > taken (maintainer of the forked becoming mostly MIA) > > It also depends how many patches you end up with, I haven't checked the > mono/.net ports but if that is just a bunch of small patches then the overhead > is not worth the pain, if there are lots of patches then sure maintaining your > repo is simpler. > > Depending on how active you (the team) are and how close to the upstream you > are > one can also see those repositories as "temporary" until all the amount of > patches are upstreamed and when done the ports can switch back to the official > distfiles (this is always a goal for ports upstreaming all our patches so we > can > remain as close as possible from the vanilla sources) > > That said I do applause the effort. As a conclusion do what ever you think is > the easiest mechanism for you as long as things like monodevelop and friends > can > be pushed in a working state again. > > Best regards, > Bapt Thanks for the input everyone. I think the overhead of keeping volatile patches in a globally accessible area is worth while. One of the things I struggled with historically is how to share my local changes that I couldn't commit to the svn tree. I have created an open source organization called FreeBSD-DotNet in Github. I have differentiated from the Mono moniker because the merging of the frameworks is inevitable with the purchase of Xamarian. I went a little crazy and forked a whole bunch of stuff, which I now think is a bad idea. The only thing that currently requires customization would be the ports tree itself (MonoDevelop doesn't build yet, but I haven't needed to change any code). However, I think we can put a bunch of how-to and wiki stuff in there for the development efforts. SO, with that: Anyone wishing to join the FreeBSD-DotNet organization can go to https://github.com/FreeBSD-DotNet and send a request. I'll try to flesh out an outstanding items list that can be ratified sometime in the next couple of weeks. Thanks, 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"
good morning
Hello mono, How are you ? We are one of the manufacturers for injection mold and injection molding , metal mould and relevant metal products.rubber products. If you have any new project for this kind of the products, we would like to establish the good and long cooperation with you . Pls kindly send us the 2D/3D drawings with detailed requirement. Looking forward to hear from you. With best regards Paul General Manager AAA MOULD INDUSTRIAL CO.,LTD. Add: RM1107,Shuanglong Internatinal,No.2. Xintang Str. Longgang.Shenzhen.China. Email:mana...@aaamould.com, aaamo...@163.com, Skype: aaamould1, wechat:paulchinamold. ___ 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: Maintaining mono/.net
On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: > Hello Ports Team, > > A couple of us on the freebsd-mono@ mailing list are having a > discussion on how best to maintain the mono ports/.net ports. One of > the things that has come up is maintaining the patches for "all this > stuff". The current paradigm in FreeBSD as I understand it is to use > the files directory and apply the patches to the port via svn/ports > tree. However, with the ubiquity of GitHub in opensource, it now seems > to be feesable to simply create a Github accound to maintain a bunch > of forked repositories (which is essentially a patched git > repository!). This makes it easier to create and apply patches and > gives us the natural path to push things back upstream. In the end, we > would just pull from the FreeBSD specific repository, which is no > different than, say, pulling from the mono project directly. > > This email is a request for response from anyone on the ports team (or > FreeBSD general) to give some input as to the acceptability of this > solution, as well as any "gotchas" we haven't thought of yet. Thanks > in advance! > There are absolutely nothing against this. Actually some ports were already doing that before the github era :D The only difficulty the history told us is : when active people get less active for various reasons you need to make sure enough people continues to get access to the said repo. Tracking upstream updates because more complicated for people not in the team (we already saw in the past ports stucked for more than 5/6 years actions being taken (maintainer of the forked becoming mostly MIA) It also depends how many patches you end up with, I haven't checked the mono/.net ports but if that is just a bunch of small patches then the overhead is not worth the pain, if there are lots of patches then sure maintaining your repo is simpler. Depending on how active you (the team) are and how close to the upstream you are one can also see those repositories as "temporary" until all the amount of patches are upstreamed and when done the ports can switch back to the official distfiles (this is always a goal for ports upstreaming all our patches so we can remain as close as possible from the vanilla sources) That said I do applause the effort. As a conclusion do what ever you think is the easiest mechanism for you as long as things like monodevelop and friends can be pushed in a working state again. Best regards, Bapt signature.asc Description: PGP signature
Re: maintaining ports and mono
Hi Romain, Just wondering about getting the mono port updated to 4.4 now that it is stable. What needs done to update this? Is any help required? Thanks, Chris On Sun, Jun 19, 2016 at 9:29 AM Romain Tartière wrote: > On Thu, Jun 16, 2016 at 01:29:08PM -0700, Russell Haley wrote: > > […] It looked very promising until I hit the > > main/external folder: > > > > https://github.com/mono/monodevelop/tree/roslyn/main/external > > 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` > > -- > Romain Tartière http://people.FreeBSD.org/~romain/ > pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) > (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) > ___ 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: Maintaining mono/.net
On 06/27/2016 20:21, Kurt Jaeger napisa: Hi! A couple of us on the freebsd-mono@ mailing list are having a discussion on how best to maintain the mono ports/.net ports. One of the things that has come up is maintaining the patches for "all this stuff". The current paradigm in FreeBSD as I understand it is to use the files directory and apply the patches to the port via svn/ports tree. However, with the ubiquity of GitHub in opensource, it now seems to be feesable to simply create a Github accound to maintain a bunch of forked repositories (which is essentially a patched git repository!). From my point of view, while not perfect, it sounds reasonable. We are open for all (good) ideas (good in sense: easier to use, requiring less effort to maintain patches) :-) ___ 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: Latest MonoDevelop Progress
On 06/27/2016 18:10, Russell Haley napisa: ... patches, instead of doing it through svn patches. It will make everything WAY easier to push back upstream. Not that it matters, eh, Ivan? :0) I already see who is to be in charge of pushing everything upstream :-P ___ 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"
