Hi, > On 17 Jan 2018, at 11:45, Denis Kudriashov <[email protected]> wrote: > > Hi > > 2018-01-17 7:15 GMT+01:00 Max Leske <[email protected] > <mailto:[email protected]>>: > Hi Martin, > > What I do is > 1. update local pharo repository on branch 'development' > 2. add repository to Iceberg > 3. create branch for phogbugz issue > 4. make changes (e.g. load stuff from your project) > 5. Note that you will have to handle addition and removal of packages > separately: > 5.1 addition: click 'add package' > 5.2 removal: click 'remove package'. You will have to commit the > removal from the command line, as Iceberg does not currently recognize > removals as staged changes. > I usually just make a second commit with the removal before I > push everything. > 6. Now the changes may not show up. But you can right click on the repository > in Iceberg and select 'Synchronize full repository' > 7. Select the changes you want to commit > > I think the 4-th step is the question. > Epicea in image is managed by Iceberg and hosted in github. How to load new > version from external monticello repo? Also there is no ConfigurationOfEpicea > in the image.
Epicea is also integrated on Pharo, and as Fuel or GT, they are managed outside. So, what you do is: - load new version of Epicea (that will be apply the changes) using a regular baseline or configuration of package by package, from Martin’s repository. - you add and remove new/removed packages AND you modify BaselineOfIDE (or the one where Epicea is declared) than you are ok to use “Sync full changes” as Max said. cheers, Esteban > > > The rest you know, I guess ;) > > Cheers, > Max > > > > On 16 January 2018 at 20:16:22, Martin Dias ([email protected] > <mailto:[email protected]>) wrote: > >> Hi, I followed the guide and everything is good. What I don't know is how to >> upgrade an external project already integrated in Pharo 7 (Epicea). I have >> new version 8.2.6. >> >> Cheers, Martín. >> >> On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <[email protected] >> <mailto:[email protected]>> wrote: >> EstebanLM wrote >> >> Mmm. I think this is because your local clone is outdated. >> >> It should be fixed with a fetch… from pharo-project, I mean :) >> >> That worked. Thanks. Next problem: Iceberg is showing a massive number of >> changes when syncing with pharo fork on the dev branch at the same commit as >> the image. There doesn't seem to be a way to collapse the whole tree making >> it impossible to find the real changes. I assume it's that known bug where >> the first commit will sync the list, but not very user friendly! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >> >> >
