Hi. I promised earlier this week to document how to remove a package from trunk. ----- To remove a package from trunk: 1. First, do NOT delete the package from source.squeak.org! Leave it in for older images. 2. Note the version of the package to be removed. 3. Edit the Squeak-Version package, altering the postscript to remove the package (MCPackage named: 'Universes') unload. You get to the postscript by pressing the 'Scripts' button in the Monticello Browser when the package is selected. 4. Save the Squeak-Version package to trunk with a version that is increased by the removed package version (step 2 above) + 1 for this bump. This keeps the trunk version number correctly increasinglike it should. 5. Update the trunk update config with the latest version of packages - and REMOVE the package from the config that should no longer be in trunk. Save this update. 6. Test it with a new image to verify everything worked correctly. -----
Comments are welcome. If no comments/correction, could this be added to the page http://squeak.org/development_process/ to increase the dev process documentation?
Thanks, cbc
On 10 February 2018 at 22:08, Chris Cunningham cunningham.cb@gmail.com wrote:
Hi. I promised earlier this week to document how to remove a package from trunk.
To remove a package from trunk:
- First, do NOT delete the package from source.squeak.org! Leave it in
for older images. 2. Note the version of the package to be removed. 3. Edit the Squeak-Version package, altering the postscript to remove the package (MCPackage named: 'Universes') unload. You get to the postscript by pressing the 'Scripts' button in the Monticello Browser when the package is selected. 4. Save the Squeak-Version package to trunk with a version that is increased by the removed package version (step 2 above) + 1 for this bump. This keeps the trunk version number correctly increasinglike it should. 5. Update the trunk update config with the latest version of packages - and REMOVE the package from the config that should no longer be in trunk. Save this update. 6. Test it with a new image to verify everything worked correctly.
Comments are welcome. If no comments/correction, could this be added to the page http://squeak.org/development_process/ to increase the dev process documentation?
Sounds good :)
Maybe someone could edit the page on github? Pull requests welcome :)
https://github.com/squeak-smalltalk/squeak.org/blob/master/_pages/developmen...
- Bert -
squeak-dev@lists.squeakfoundation.org