From owner-freebsd-ports@FreeBSD.ORG Wed Mar 27 16:37:48 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DEF4BFB6 for ; Wed, 27 Mar 2013 16:37:48 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by mx1.freebsd.org (Postfix) with ESMTP id A6183BFF for ; Wed, 27 Mar 2013 16:37:48 +0000 (UTC) Received: by mail-ve0-f169.google.com with SMTP id d10so3468690vea.14 for ; Wed, 27 Mar 2013 09:37:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=tx1P/8WRkn6GUjEOqPQDYzU9W1q23LxcHV7jDeaYL78=; b=c56Mpz35fHWWGbgUKf3XHzkbyspjDbNqPj65bU2E1vFNtPiPAJbN25Ss0aL5ve9Cxz E6VWS/qn/OI6xl7fdqUQvk7ilNVbeAuzKEAlnL8d2/MEhL3GLwgum34OfG0MEemQtTrH 341QjeZTpCex65gR/CKQbdpmmhWHX15RdPnzGmtMZwM7dgRphdTMXo2zV7lBZ464Niyk si6ue3XRnZu3tmoouimrFC15ZRaM960oHp6NsjDHLC7rmq/LfiSs+MtrXv4mBKAXpMMP O01jR6ir1AlZTeHzKcvyBwAv9M0w2AAwDzI6W67TEACUfdhsCAJQBk/FX+1lBZ2HF/xN UdfQ== MIME-Version: 1.0 X-Received: by 10.58.212.8 with SMTP id ng8mr10528608vec.25.1364402262652; Wed, 27 Mar 2013 09:37:42 -0700 (PDT) Received: by 10.220.115.7 with HTTP; Wed, 27 Mar 2013 09:37:42 -0700 (PDT) In-Reply-To: References: <20130326082325.GW2198@droso.net> Date: Wed, 27 Mar 2013 12:37:42 -0400 Message-ID: Subject: Re: Status of packages From: grarpamp To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Mar 2013 16:37:48 -0000 >> 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. 'formal/project/service' and 'flux' were attempts at covering this. Another partial example might be pointyhat, the logs are viewable, but not the output file trees. The 'security' aspect would just seem whether the builds come from the main repo and are built in a pretty automated sandbox, or from joe's working tree in their own slush account.