Changes between Version 2 and Version 3 of HaikuPorterForPM/Repository

Timestamp:

06/12/13 06:46:38 (2 years ago)

Author:

zooey

Comment:

--

HaikuPorterForPM/Repository

@@ -1 +1 @@
 = Repository =
 
-The main purpose of !HaikuPorter is to build a concrete set of packages (i.e. using specific port versions) in a controlled environment, such that the building process is repeatable. 
+The main purpose of !HaikuPorter is to build a concrete set of packages (i.e. using specific port versions) in a controlled environment, such that the building process is repeatable. The concrete set of package versions and their resulting packages corresponds to the online package repository from which users can download packages.
+
+To implement the concept of a package repository, !HaikuPorter makes use of two specific folders in the ports tree.
+
+== The `repository` Folder ==
 
 As build recipe files may exist for many different versions of a port, the active version(s) need to be selected from them. As this is a somewhat expensive process, !HaikuPorter caches the set of package versions that are to-be-built in a particular ports tree in the `repository`-folder of that ports tree.
@@ -11 +15 @@
  Note:: Currently, !HaikuPorter only supports a single active version of a port, but that is likely to be changed in the future).
 
+== The `packages` Folder ==
+
 Built packages are being collected into the `packages`-folder of the ports tree. The packages in this folder are meant to be uploaded into the corresponding package repository (from where packages will be downloaded by the user). Because of that, it is important that the set of packages in the repository folder is consistent with respect to declaration of provides, requires, conflicts, etc. This does not have to be the case when you are working on new recipes, but it should be the case again, before you push your changes.