From owner-freebsd-ports@FreeBSD.ORG Tue Mar 25 01:15:24 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CDA41065671; Tue, 25 Mar 2008 01:15:24 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mta3.srv.hcvlny.cv.net (mta3.srv.hcvlny.cv.net [167.206.4.198]) by mx1.freebsd.org (Postfix) with ESMTP id C0DDD8FC29; Tue, 25 Mar 2008 01:15:23 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from flosoft.no-ip.biz (ool-435559b8.dyn.optonline.net [67.85.89.184]) by mta3.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JY900MG0I564508@mta3.srv.hcvlny.cv.net>; Mon, 24 Mar 2008 21:15:09 -0400 (EDT) Received: from flosoft.no-ip.biz (localhost [IPv6:::1]) by flosoft.no-ip.biz (8.14.2/8.14.2) with ESMTP id m2P1F3Vo000285; Mon, 24 Mar 2008 21:15:05 -0400 Date: Mon, 24 Mar 2008 21:14:58 -0400 From: "Aryeh M. Friedman" In-reply-to: To: Ivan Voras Message-id: <47E85212.1070905@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT X-Enigmail-Version: 0.95.6 References: <47E30FB4.1000205@gmail.com> User-Agent: Thunderbird 2.0.0.12 (X11/20080314) Cc: freebsd-ports@freebsd.org Subject: Re: SoC Project: Ports 2.0 engine X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2008 01:15:24 -0000 Ivan Voras wrote: > Aryeh M. Friedman wrote: >> School ate any free time I had to work on ports 2.0. For this >> reason I would like to find some way to make it a Summer of Code >> project. Kip Macy has provisionally agreed to mentor it if a) it is >> approved by Google and FreeBSD, b) No one more qualified steps forward. >> >> Project goals (SoC portion): >> >> 1. Impliment beta quality version of the engine (see "Recursive >> Make Considered Harmful" for main points) > > I can't find the post with this title, but I think I get what you mean :) http://aegis.sourceforge.net/auug97.pdf > >> 2. Use the engine to build xorg and all ports it depends on >> >> 3. Creation of compatibility layer >> >> What do people think and should I proceed with submitting a >> application to Google? > > Go for it :) > > I'd like to suggest two of the major features that a new ports system > should have: > > - reliability (almost in the database "ACID" sense; for example that > no half-registered packages are created by issuing Ctrl-C in a > critical moment) > - parallel builds of as much as possible; at least parallel builds of > independent dependencies and if possible also of ports themselves > (probably by adding an opt-in flag in Makefile to signal if the port > supports "make -j" for its build phase). These two items are being handled in a different (but hopefully cordinated) project http://wiki.freebsd.org/PortsToDo > > The first one can be solved by rolling your own system which carefully > juggles atomic operations and locks or by using an already present > solution like sqlite. > If we limit it only to top level stuff then it is not that bad I think.... if you want more details I can forward some private conversation between me and the person working on the above project