From owner-freebsd-mono@freebsd.org Wed Jun 29 05:46:10 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 E8144B84AC5; Wed, 29 Jun 2016 05:46:10 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A357F2F77; Wed, 29 Jun 2016 05:46:10 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x22d.google.com with SMTP id j3so52112242vkb.0; Tue, 28 Jun 2016 22:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Sfb08UBTUV6cLvNA2ccs05FExVj5zWh2bZTyFSFzcRY=; b=v/DB9rP974/4pFRrFGqAjEbru1Mvg9tBYRXLge17qrukp8xezgkEHCkeeLv8MLC+M7 GhgaifkinUXPjoYzPLW8fwbcQWz7c+7LQORUQQgVyieQXYx/yK48O0KZIun4qBY8AvNA 6dIfGWZrNem3BO/JENlV4qS2mnH0XHRG9AXf8EF2gLkMpSS84QGMjsig+2wcKv0mzNIk O9zV5I0InApoOpxGNhNPhAP/hMgY999RhHQQwN1oTTlGVl6EYktg0EmfVHTE3jgdmAK1 mREF99rCQ0qRg0uf32+40O+QG5HWyZ2M6CyaitSyiY4IjyxAJC9iF2h4AVDZJNZ6yw/V mA8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Sfb08UBTUV6cLvNA2ccs05FExVj5zWh2bZTyFSFzcRY=; b=SJjEDTl0bGvkTr0EvWCdwdutdHwzgZUbDly+BDfAJ+bSK0VchrU6No0GhPeZbbL0CJ YaByJMxtZxSHWR89KP6TKpFBnBRmuGthrte+nU4QeabSEHIioIE/wC7aPtxVQ746aM4u m8kWfGBVIGkOkHVnXiykBVMVZj0UjbaaPol1YvXVpjnyPnNY+7zDNK07/rdDbYmjAsd0 7XXio2shq39EBy4p3WFlSf2byQF5RUblFXSRqlDQ2VhMi2CRYzxroYR/r2j6tbDb+QGt B1sZyOdvRoBHCKW+o8KwxQ0bFu18lqjrPgZvVFVIyEoRLOm+0B+/z+/uyLdBdh6D14+P nYRg== X-Gm-Message-State: ALyK8tJW1Pcxec9pPvr3LQC0DuRsozQMKStkPOU3nGqRaMzcxjb2d06KZ3nX6om3EFotHFCY2Z1N2tFqHbLZug== X-Received: by 10.159.34.104 with SMTP id 95mr2773452uad.86.1467179169626; Tue, 28 Jun 2016 22:46:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.54.196 with HTTP; Tue, 28 Jun 2016 22:46:09 -0700 (PDT) In-Reply-To: <20160628094307.bepxy46dp5igizeh@ivaldir.etoilebsd.net> References: <20160628094307.bepxy46dp5igizeh@ivaldir.etoilebsd.net> From: Russell Haley Date: Tue, 28 Jun 2016 22:46:09 -0700 Message-ID: Subject: Re: Maintaining mono/.net To: Baptiste Daroussin Cc: freebsd-ports@freebsd.org, Freebsd-mono Content-Type: text/plain; charset=UTF-8 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: Wed, 29 Jun 2016 05:46:11 -0000 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