Changes between Version 6 and Version 7 of Obsolete/MovedToTree/PackageManagement/Infrastructure

Timestamp:

Nov 4, 2013, 9:07:07 AM (11 years ago)

Author:

zooey

Comment:

--

Obsolete/MovedToTree/PackageManagement/Infrastructure

@@ -88 +88 @@
 The repositories are maintained via files in the Haiku git repository. For each architecture and each repository the Haiku git repository contains a file listing the packages for that repository. For the HaikuPorts repositories the packages are listed with the respective version. For the Haiku repositories the version is implied.
 
-Whenever a developer wants to update or add a HaikuPorts package, the new package file has to be uploaded to their vmrepo.haiku-os.org account and the package list file for the repository has to be adjusted accordingly. A helper script is provided to perform both steps. Afterward the change needs to be committed and pushed to vmrepo.haiku-os.org. The push hook on the server analyzes the change, moves the new package file from the developer's account to the repository directory, and builds a new repository snapshot. If the package file is missing or broken, the push is rejected with a message notifying the developer about the problem.
+Whenever a developer wants to update or add a HaikuPorts package, the new package file has to be uploaded to their git.haiku-os.org account and the package list file for the repository has to be adjusted accordingly. {{{jam upload-packages <packages-list>}}} can be used in order to upload the package(s) or the packages could just be {{{scp}}}'ed into the 'hpkg-upload' folder in the developer home directory on git.haiku-os.org. When that is done, the change can be pushed to git.haiku-os.org, where a push hook will analyze the change, move the new package file(s) from the developer's account to the repository directory, and build a new repository snapshot. If a package file is missing or broken, the push will be rejected with a message notifying the developer about the problem.
 
 The creation and update of repositories for official releases has to be triggered explicitly on the server. In either case the Haiku repository is built by the build service.