What is the problem with ports PR reaction delays?
aryeh.friedman at gmail.com
Mon Jan 27 16:37:37 UTC 2014
Sorry was just putting why I used the mentioned ports in context (I believe
in real life examples instead of made up ones for that)... any other
mention of it in the thread was only because it was a convenient example
that didn't violate an nda or something else.
On Mon, Jan 27, 2014 at 11:29 AM, Lars Engels <lme at freebsd.org> wrote:
> Am 2014-01-25 05:30, schrieb Aryeh Friedman:
> On Fri, Jan 24, 2014 at 11:16 PM, Alfred Perlstein <alfred at freebsd.org
>>> (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
>> 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
>> port should be delegated to whatever build scripts it uses the idea is
>> that the entire port system be considered as a single graph... side note
>> use devel/cook and devel/aegis to maintain and build petitecloud on.
> would you please stop spamming about petitecloud in _every single_ mail
> sending to some list?
> Thank you.
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
More information about the freebsd-ports