Date: Sun, 14 Jun 2015 16:36:08 +0200 From: Michelle Sullivan <michelle@sorbs.net> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: OpenSSL Security Advisory [11 Jun 2015] Message-ID: <557D9158.9060309@sorbs.net> In-Reply-To: <557D89B9.7000502@FreeBSD.org> References: <201506131950.t5DJooEA021169@gw.catspoiler.org> <557CB34E.9090708@sorbs.net> <CAF6rxgnokxs=Mb29KcDP09z5dBdaPtEXOhgaWdRmYqMssFxr5g@mail.gmail.com> <557CBFC2.6040003@sorbs.net> <557D89B9.7000502@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman wrote: > On 13/06/2015 19:41, Michelle Sullivan wrote: > >> How about one for how to make your own portsnap ? :P >> > > Presumably you're wanting to re-distribute local modifications to the > ports tree sources around your machines? > > One relatively easy way to do that is to grab the ports from GitHub -- > > https://github.com/freebsd/freebsd-ports > > to a machine you designate as your local github master. You can create > your own branch for your modifications and distribute that around your > systems. Plus you get all the normal merging and revision control > features of git. > > Although personally I tend not to put a ports tree on anything except a > package building server nowadays. > > Cheers, > > Matthew > > I have my own SVN server however it's incredibly slow when compared to portsnap ... would like to know how the portsnap server is built so I can portsnap my own tree... Michelle -- Michelle Sullivan http://www.mhix.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?557D9158.9060309>