Changes between Version 3 and Version 4 of HaikuPorterForPM

Timestamp:

06/12/13 10:34:59 (2 years ago)

Author:

zooey

Comment:

--

HaikuPorterForPM

@@ -20 +20 @@
   Contains recipe files for all the ports to be built
 
-== [wiki:HaikuPorterForPM/BuildRecipes Build Recipe Files] ==
+== Build Recipe Files ==
 
-For a particular version of a port a build recipe file specifies what packages shall be built for that port and the build recipe provides all required information for that purpose. 
+For a particular version of a port a build recipe file specifies what packages shall be built for that port and the build recipe provides all required information for that purpose.
 
-== [wiki:HaikuPorterForPM/PortsAndPackages Ports and Packages] ==
+More info on build recipes is available on this subpage: [wiki:HaikuPorterForPM/BuildRecipes Build Recipe Files]
+
+== Ports and Packages ==
 
 Each port will produce a set of packages, typically a base package containing the main binaries/libraries of the port plus a source and a debug package. Ports that provide libraries will usually provide an additional development package, too.
@@ -30 +32 @@
 All the packages built by !HaikuPorter are being collected in the 'packages'-folder of the ports tree.
 
-== [wiki:HaikuPorterForPM/Repository The Package Repository] ==
+More info on ports and their packages is available on this subpage: [wiki:HaikuPorterForPM/PortsAndPackages Ports and Packages]
 
-For each port, the most current version that has been marked as stable for the Haiku platform !HaikuPorter is running on will be considered the active one. For all active ports, a [http://dev.haiku-os.org/wiki/PackageManagement/BuildingPackages#The.PackageInfo .PackageInfo]-file will be put into the `repository`-folder of the ports tree. Only this set of active package-infos will be considered during dependency resolution.
+== The Repository ==
 
-The 'repository' folder defines which set of packages will finally be uploaded into the corresponding package repository (from where packages will be downloaded). 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.
+For each port, the most current version that has been marked as stable for the Haiku platform !HaikuPorter is running on will be considered the active one. For all active ports, a [http://dev.haiku-os.org/wiki/PackageManagement/BuildingPackages#The.PackageInfo .PackageInfo]-file representing that to-be-built package will be put into the `repository`-folder of the ports tree. Only this set of active package-infos will be considered during dependency resolution among ports.
 
-Packages for other versions of a port can be built, but only if their dependencies can be resolved by the repository. If that is not the case and you really need to build a specific version of a package, then you can do so by checking out a (git-)revision of the ports tree where that package version was the active one.
+More info on the repository is available on this subpage: [wiki:HaikuPorterForPM/Repository The Repository]
 
-== [wiki:HaikuPorterForPM/HandlingRequirements] ==
+== Handling Requirements ==
 
 === !HaikuPorter ===
@@ -53 +55 @@
  * XZ-utils (for a port that comes as a '*.xz' archive)
  * the sources of ports are only available as VCS-checkout, so any of these VCS might be required:
-   * bzr
-   * CVS
+   * bzr/Bazaar
+   * cvs
    * fossil
    * hg/Mercurial
@@ -61 +63 @@
 === Requirements defined by a recipe file ===
 
-All packages listed as requirements in a port's RecipeFile will be resolved automatically by !HaikuPorter and the ports will be built in the correct order.
+In order to be able to automatically resolve dependencies and build ports in the correct order, !HaikuPorter relies on the build recipe files to actually declare those dependencies. Haiku's [http://dev.haiku-os.org/wiki/PackageManagement/PackagingPolicy packaging policy] strongly advises packagers to declare dependencies on specific commands and libraries, not on other packages.
 
-== [wiki:HaikuPorterForPM/Usage Usage] ==
+More info on how to handle requirements is available on this subpage: [wiki:HaikuPorterForPM/HandlingRequirements Handling Requirements]
 
-'haikuporter -h' will show usage info.
+== Usage of !HaikuPorter ==
+
+`haikuporter -h` will show usage info, more detailed usage information is given on this subpage: [wiki:HaikuPorterForPM/Usage Usage].
 
 In order to build a port, just use 'haikuporter <portName>'