Date: Tue, 28 Jun 2016 09:48:17 +0200 From: Ivan Radovanovic <radovanovic@gmail.com> To: Kurt Jaeger <lists@opsec.eu> Cc: Russell Haley <russ.haley@gmail.com>, Freebsd-mono <freebsd-mono@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Maintaining mono/.net Message-ID: <57722BC1.5050307@gmail.com> In-Reply-To: <20160627182124.GA79889@home.opsec.eu> References: <CABx9NuSwbf2jwyqcGNGeyWjJ4pbVFmCiGO=i172UDFy2=yGPOw@mail.gmail.com> <20160627182124.GA79889@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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) :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57722BC1.5050307>