From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 04:30:33 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED584EEE; Sat, 25 Jan 2014 04:30:32 +0000 (UTC) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB46C1CF8; Sat, 25 Jan 2014 04:30:32 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id um1so3941294pbc.5 for ; Fri, 24 Jan 2014 20:30:32 -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=gU4uizpVKfwubCIHT5VrL+FZG0EoJ4OGwhKW7uGvG5c=; b=q2OFUg/f878K4D72MyZudBw9D3O8UtTZBI43GM9yEy73dCrjiaOEE4jWfXPoG2snEC 79epRnlSa9Osmew/MwhpbzTzIPYHruioYOhqcG4NlNQZlLd6PCBip/o5Qw/ALABhSe0y vSx5JH+Wsf8g4PpJu3wKViXJ8E0PeuQjjCRrlqaPB6vd/Fj7W0jIf3xKCQK8J9FqyIl/ Z5gUvOVpQIy9jaCGI0ti2YJbd9v9u2/g6F6Uc6D2TFct5hXZdDnGkmjhaJcaZVjXooPV MKcki/0bN/73Y/Azz2E6At4M6b1y9h8CiFVpxC5tSqv/fm+oIcxAvPuX7V/lpIeyhHec 8loA== MIME-Version: 1.0 X-Received: by 10.69.19.235 with SMTP id gx11mr7814485pbd.114.1390624231726; Fri, 24 Jan 2014 20:30:31 -0800 (PST) Received: by 10.68.155.38 with HTTP; Fri, 24 Jan 2014 20:30:31 -0800 (PST) In-Reply-To: <52E33AA7.3080205@freebsd.org> References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> Date: Fri, 24 Jan 2014 23:30:31 -0500 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Aryeh Friedman To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Ports ML 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: Sat, 25 Jan 2014 04:30:33 -0000 On Fri, Jan 24, 2014 at 11:16 PM, Alfred Perlstein wrote: > > > (maybe there is some great ports system that I'm not aware of that makes > this all as easy github, but I somehow doubt that.) Nice to be able to plug something other then petitecloud as a possible solution to this... namely as far I can tell from previous discussions and such that the port system is nothing more then a very large DAG (directed acyc. graph) the author of devel/cook (and devel/aegis) wrote an incredible paper showing why Make (in any form) will never be upto the task ( http://aegis.sourceforge.net/auug97.pdf )... there are several solutions that use this paper as their foundation in the ports system (devel/cook, devel/cons, devel/scons)... don't get me wrong the actual building of each port should be delegated to whatever build scripts it uses the idea is only that the entire port system be considered as a single graph... side note we use devel/cook and devel/aegis to maintain and build petitecloud on. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org