From owner-p4-projects@FreeBSD.ORG  Sun May 30 01:57:38 2010
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 449291065678; Sun, 30 May 2010 01:57:38 +0000 (UTC)
Delivered-To: perforce@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 090981065676
	for <perforce@FreeBSD.org>; Sun, 30 May 2010 01:57:38 +0000 (UTC)
	(envelope-from jlaffaye@FreeBSD.org)
Received: from repoman.freebsd.org (unknown [IPv6:2001:4f8:fff6::29])
	by mx1.freebsd.org (Postfix) with ESMTP id EA8118FC12
	for <perforce@FreeBSD.org>; Sun, 30 May 2010 01:57:37 +0000 (UTC)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id o4U1vbEs051837
	for <perforce@FreeBSD.org>; Sun, 30 May 2010 01:57:37 GMT
	(envelope-from jlaffaye@FreeBSD.org)
Received: (from perforce@localhost)
	by repoman.freebsd.org (8.14.3/8.14.3/Submit) id o4U1vbnm051835
	for perforce@freebsd.org; Sun, 30 May 2010 01:57:37 GMT
	(envelope-from jlaffaye@FreeBSD.org)
Date: Sun, 30 May 2010 01:57:37 GMT
Message-Id: <201005300157.o4U1vbnm051835@repoman.freebsd.org>
X-Authentication-Warning: repoman.freebsd.org: perforce set sender to
	jlaffaye@FreeBSD.org using -f
From: Julien Laffaye <jlaffaye@FreeBSD.org>
To: Perforce Change Reviews <perforce@FreeBSD.org>
Precedence: bulk
Cc: 
Subject: PERFORCE change 178963 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 May 2010 01:57:38 -0000

http://p4web.freebsd.org/@@178963?ac=10

Change 178963 by jlaffaye@gsoc on 2010/05/30 01:57:14

	Plans and thoughts for complete packages support.

Affected files ...

.. //depot/projects/soc2010/pkg_complete/Milestones#2 edit

Differences ...

==== //depot/projects/soc2010/pkg_complete/Milestones#2 (text+ko) ====

@@ -1,0 +1,26 @@
+pkg_create:
+	The options of pkg_create are useless for creating a complete package.
+Should we add support for complete package in pkg_create or into a new tool?
+The tool for creating a complete package would take for first argument the meta
+(traditionnal) package. Then the tool read the plist to look for @pkgdep and 
+repeat the operation for each dependency.
+After ordering the dependencies, the tool tar'up all the traditionnal packages 
+(without compression as the packages are already bz'ed).
+This step would require factorisation of the code in pkg_info into a libpkg
+function, with libarchive support for efficiency.
+
+ports tree:
+	Add a "complete-package" target which depends on package-recursive and
+call the tool of step 1.
+
+pkg_add:
+	Add simple routine to test if the package is a traditionnal or complete package.
+If the package is complete, loop over the traditionnal packages in it,
+call the function to install a traditionnal package (this function may work
+with streams). If the package is tradionnal, pass directly the stream to the 
+function.
+As a side effect, remove playpen and embrace libarchive.
+
+pkg_info:
+	Show if the package is complete (list of contained packages) or the 
+info of the traditionnal package.