Date: Mon, 27 Jun 2016 20:21:24 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Russell Haley <russ.haley@gmail.com> Cc: freebsd-ports@freebsd.org, Freebsd-mono <freebsd-mono@freebsd.org> Subject: Re: Maintaining mono/.net Message-ID: <20160627182124.GA79889@home.opsec.eu> In-Reply-To: <CABx9NuSwbf2jwyqcGNGeyWjJ4pbVFmCiGO=i172UDFy2=yGPOw@mail.gmail.com> References: <CABx9NuSwbf2jwyqcGNGeyWjJ4pbVFmCiGO=i172UDFy2=yGPOw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- pi@opsec.eu +49 171 3101372 4 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160627182124.GA79889>