From owner-freebsd-ports@FreeBSD.ORG Fri Jan 24 23:45:38 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 147B927C for ; Fri, 24 Jan 2014 23:45:38 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE3321575 for ; Fri, 24 Jan 2014 23:45:37 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id q10so3646823pdj.24 for ; Fri, 24 Jan 2014 15:45:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kp3xZSTgDcSRnyGmbAjlBlosEwXrI+8VgnyivEp+CYw=; b=ugkAEQprikrBjLvE3KE4XwPQkIZS0F+JpVkZ/Eo50fIJvmIjCVBt+L22bsEt9Sxrec lvZIDjF/JLi4la6gOMHhxGMWEnBDdp6N4OwvaFlQgtF2sFwBTnT/64z/268RehrPUQ2X abEIrK5QCbIs2VdLNFcTHIoJsB4F14P4Ig3pXJkyd/6GQGmYuy8EjcfJZ1t4HzGN4dVv p4wAccTLlmPVWWxRKMsTdOypxU8TJUrFq3L2X5YfL7prUgNDxBm5DPjKPqhVzmnty6Vx WvU3PdWtNbcePpTFqUSTByR0BXVTqdGUYzeSF835STjAfTEOpQafokhwYoVmHcOLLQ5t Ys7Q== MIME-Version: 1.0 X-Received: by 10.66.16.131 with SMTP id g3mr16996408pad.138.1390607137494; Fri, 24 Jan 2014 15:45:37 -0800 (PST) Received: by 10.68.155.38 with HTTP; Fri, 24 Jan 2014 15:45:37 -0800 (PST) In-Reply-To: References: Date: Fri, 24 Jan 2014 18:45:37 -0500 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Aryeh Friedman To: Big Lebowski Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 23:45:38 -0000 On Fri, Jan 24, 2014 at 6:30 PM, Big Lebowski wrote: > Hi everyone, > > I wanted to ask about the growing time of reaction to ports PR's - what is > the problem? It seems to me, as a ports contributor, that this time is only > growing, not shrinking, and there's no formal/automated procedures that > would help in managing the issue. > > Today I found myself fighting with ezjail only to discover it has issues > working on FreeBSD 10.0-R. Great, I thought, there must be something else, > so I went to make the research. It appears there isnt much more, and the > alternatives are qjail that seems to be quite dated and zjails, that's not > in ports. Not long after looking into zjails, what seems to be a great > tool, I found its port submission sits there since... September 2013. Now, > given the fact the Docker is on mouth of everyone, and containers are > getting a lot of attention, FreeBSD looks really bad with no tools to > manage such great technology like Jails, especially when ezjail, unofficial > industry standard to manage jails, is now broken and zjails waits to be > accepted (or even rejected) for so much time. > > Why not test on a VM instead of a jail it seems this is a even more accurate test because you can run bare metal installs (I have run to some ports [including some of my own]) that worked with jail/tinderbox but failed a full bare metal install. Take a look at -virtualization@ for ideas, the proposed handbook entry on virtualization ( http://www.petitecloud.org) or just use a front end like petitecloud (yes yet an other port waiting for comitting [one this one there are some bugs though]) What is the problem? Isnt there enought commiters? Isnt there a automated > PR handling procedure reminding commiters with relevant access about such > submissions? Can we help? I hope to spark some discussion. > I have made a couple of scripts for automated this for specific ports but not for all (the VM test method)... if you want I can post them (they are high;y specific to installing the petitecloud port though) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org