Skip to content

Package migration process

Jump to bottom Edit New page
Gary Ewan Park edited this page Feb 10, 2017 · 46 revisions

When migrating a package from an existing Chocolatey Package Repository, there are a number of things that need to be done. These set of guidelines list the things that should be done during that process to ensure that it goes as smoothly as possible.

  1. Make sure to contact the existing package maintainer to ensure that they are on-board with migrating the package to this repository.
  2. Create a PR to the existing Chocolatey Package Repository to remove the package. This will include:
  • Deleting all package source files.
  • If the package is using ketarin:
    • Remove the ketarin.*.xml file.
    • If the _output folder is checked into the repository, delete the folder associated with the package.
  • Leave the icon used by the package in place, this will mean that old package versions will still have a valid URL.
  1. Create a PR to this repository for the package with the following notes:
  • Collect all relevant package data and put it in this repositry. Without any changes make first commit. This represent original package from remote repository.
  • Following all guidelines listed here.
  1. Discuss with the existing maintainer if they want to remain a package maintainer. If not, remove the maintainer from the nuspec file, and from chocolatey.org for that package.
  2. Add the chocolatey user as a maintainer in both the nuspec and on chocolatey.org.
  3. Once the PR to the existing Chocolatey Package Repository has been merged, the PR to this repository can be merged.
  4. If there are existing issues/PR's on the existing package repository for the package being migrated, these should be transferred/linked to this repository, and worked on here.

Packages not migrated

Currently the following packages have not been migrated to AU, any help in migrating these packages will be greatly appreciated.

Add a custom footer
Add a custom sidebar
Clone this wiki locally