From owner-freebsd-ports@FreeBSD.ORG  Mon Jan 27 16:29:06 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 613DAB27
 for <freebsd-ports@freebsd.org>; Mon, 27 Jan 2014 16:29:06 +0000 (UTC)
Received: from mail.0x20.net (mail.0x20.net [217.69.76.211])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 22C3B18FE
 for <freebsd-ports@freebsd.org>; Mon, 27 Jan 2014 16:29:05 +0000 (UTC)
Received: from 0x20.net (0x20.net [217.69.76.212]) (Authenticated sender: lala)
 by mail.0x20.net (Postfix) with ESMTPA id 8C55D6A6006
 for <freebsd-ports@freebsd.org>; Mon, 27 Jan 2014 17:29:04 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 27 Jan 2014 17:29:04 +0100
From: Lars Engels <lme@FreeBSD.org>
To: freebsd-ports@freebsd.org
Subject: Re: What is the problem with ports PR reaction =?UTF-8?Q?delays=3F?=
Organization: FreeBSD
In-Reply-To: <CAGBxaXm2N3mEVxQ=_oXHFEBUnY8JL4Fu+NwfrERcSbx1RmEJ1Q@mail.gmail.com>
References: <CAHcXP+f6e-t--XbQPTH1goJp_CL7P=zTj5trZVWd4YZ_EsO9gw@mail.gmail.com>
 <52E2FA36.5080106@marino.st>
 <CAHcXP+fRDeKXjz0_sifgzeXC2dA-eDnoV5NH1yvF2D6R8JRmAg@mail.gmail.com>
 <52E303CB.6020304@marino.st>
 <CAHcXP+e9p2HrQ=M9HmPecMbWtXRuYPzH9kwfLGqgdrUrhvLuEA@mail.gmail.com>
 <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org>
 <CAGBxaXm2N3mEVxQ=_oXHFEBUnY8JL4Fu+NwfrERcSbx1RmEJ1Q@mail.gmail.com>
Message-ID: <7dfba4b8e0dc222ddee8cbfe40818b16@mail.0x20.net>
X-Sender: lme@FreeBSD.org
User-Agent: Roundcube Webmail/0.7
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:29:06 -0000

Am 2014-01-25 05:30, schrieb Aryeh Friedman:
> On Fri, Jan 24, 2014 at 11:16 PM, Alfred Perlstein 
> <alfred@freebsd.org>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,

would you please stop spamming about petitecloud in _every single_ mail 
you're
sending to some list?

Thank you.

Lars