• robotpkg –( o )–
• About
• Documentation
  • General
  • Quick setup guide
  • Binary packages setup guide
  • apt repository
  • New package release checklist
  • robotpkg/wip
• Index
  • Available packages
  • Distribution files
• Bulk Builds
  • Scheduled
  • robotpkg/
  • robotpkg/wip/
  • Distfiles mirroring

The synthetic checklist for making a new package release

• Change your working directory to robotpkg/"category"/"package"
• Update your copy with git pull, optionally make a new branch with git checkout -b testing
• If needed, upload the new DISTFILES to the MASTER_SITES location
• Update version number in the Makefile
• If needed, update DEPEND_ABI in depend.mk to the oldest supported version
• Check the dependencies requirements
• Regenerate checksums with make mdi
• Check the files in patches/. If they have been merged upstream, remove them. If they don't apply with make patch, rework them.
• Regenerate checksums with make mdi if you changed any patch file.
• Check installation with make install
• Verify PLIST with make print-PLIST && diff PLIST PLIST.guess
• Optionally clean your build with make clean>
• Commit. Do one commit per package update. In the subject line, put "[category/package] Update to X.Y". In the message body, start with "Changes since Y.Z:" and the change log. Also mention any patch removal, and why they're removed.
• Send a message to robotpkg@laas.fr with a URL where to browse or fetch your commit. If you have no public URL, send a git-diff corresponding to your commits.