PERFORCE change 178963 for review

[Julien Laffaye]

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

Change 178963 by jlaffaye at 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.