Date: Tue, 26 Mar 2013 21:24:24 +0100 From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at> To: grarpamp <grarpamp@gmail.com> Cc: ports <freebsd-ports@freebsd.org> Subject: Re: Status of packages Message-ID: <CAE-m3X1sPLUywnNnvbm50i=t0L7LGVK5woN8OexqUA0PMuEh5Q@mail.gmail.com> In-Reply-To: <CAD2Ti2-3eTQ0wc-V8NLgkVANGcdigRjL5m9h_2eGFw4G=NQK5w@mail.gmail.com> References: <CAD2Ti29CQ5uchftP63niDB8ORLW7CCh%2B1qBco=P44=wtXhP7iA@mail.gmail.com> <20130326082325.GW2198@droso.net> <CAD2Ti2-3eTQ0wc-V8NLgkVANGcdigRjL5m9h_2eGFw4G=NQK5w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 26.03.2013 19:20 schrieb "grarpamp" <grarpamp@gmail.com>: > > > This may not have made it out in this list, the latest announcement is > > here http://www.freebsd.org/news/2012-compromise.html#update20130323 > > It's nice to see something like redports. It can be helpful to those using > ports to diagnose their local builds against the output of a formal sandbox > service for the project. It would be cool if the logs, build hiers and packages > from such a buildbot were accessible. They'd obviously always be in flux but > still useful to see. Redports is very bad for providing packages because of all the frequent changes and the "chaotic nature" of such a system. Additionally the security considerations made clear that redports should never provide any binary data to users to minimize risk in case of a potential security incident.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X1sPLUywnNnvbm50i=t0L7LGVK5woN8OexqUA0PMuEh5Q>