[Pharo-dev] FW: Versioning with Iceberg

Tim Mackinnon tim at testit.works
Thu May 30 03:46:58 EDT 2019


Hi - I’m rather confused reading your thread as it’s not clear what you’re doing.

Using iceberg - I typically see the normal loading progress bars for long operations on the top left of the screen - often they stack below one another to show nested operations (aside: they are a bit ugly - but it’s a consistent metaphor across Pharo). I get them when loading, pulling, pushing, diffing etc. Do you not see them?

Back to your version question - what baseline are you loading from a repo? A specific example might help.

If i were to load Exercism as an example - the following page describes how to upgrade to a specific version of the baseline in the repo.

Eg latest vs v0.2.3

https://github.com/exercism/pharo-smalltalk/blob/master/docs/UPGRADE.md


This describes how to do it in the playground - as versions are actually loaded by metacello - and Iceberg builds on top of it to route things via git and make use of version tags etc, and it then gives the push/pull/commit operations. (I’m probably describing this badly - but I suspect the confusion is in here for you).

Having loaded your particular baseline (the code tagged as v2.0.3 for example), Iceberg will let you compare it to other branches - or hash versions in git.

But typically, libraries you use will give you a playground script that specifies a stable version - you eval that in your playground and those libraries will then appear in your image (and also in Iceberg).

For your project - you can formalise those dependencies by creating your own baseline that references those scripts as well.

But maybe you can describe better what you are doing and we can unpick what is happening.

Tim

Sent from my iPhone

> On 30 May 2019, at 02:07, Shaping <shaping at uurda.org> wrote:
> 
> Sorry, I meant progress bar, not histo….
>  
> From: Shaping [mailto:shaping at uurda.org] 
> Sent: Wednesday, May 29, 2019 20:05
> To: 'Pharo Development List' <pharo-dev at lists.pharo.org>
> Subject: RE: [Pharo-dev] Versioning with Iceberg
>  
>  
>  
> From: Pharo-dev [mailto:pharo-dev-bounces at lists.pharo.org] On Behalf Of Ben Coman
> Sent: Wednesday, May 29, 2019 10:58
> To: Pharo Development List <pharo-dev at lists.pharo.org>
> Subject: Re: [Pharo-dev] Versioning with Iceberg
>  
>  
>  
> On Wed, 29 May 2019 at 23:08, Shaping <shaping at uurda.org> wrote:
> I’m finding 7.0.3 to be more stable. 
>  
> How do I load a specific baseline/version with Iceberg?  I’m getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0.  There are many differences.  I want to commit my image changes locally for now on a 7.0.3.
>  
>  
> Its not completely clear what you want.  
>  
> You can right-click a repo > Metacello > Install baseline of.....
> 
> Or right-click a repo > Repository > Remotes 
> and select one of those branches to check out.
>  
> I missed the Repository item completely, all this time.  I think I was blocking it out mentally because I was already in an Iceberg window that lists repos.  The doubling up is confusing and unexpected.   So we have Iceberg repos wrapping Git repos?  I’m not sure I have the scheme right.
>  
> Why don’t we have the usual wait-cursors appearing on long synchronous actions behind button clicks?  These lock up the system for 1 or 2 minutes often.  For example, I deleted 20-odd packages the other day and waited 2 minutes for it to finish, wondering why the system was completely unresponsive and showing no indication (no histo; no wait cursor).  This happens when cloning a Git repo, too.  The histo opens about ½ second before the about 1-m pull finishes.  This happened in the 7.0.3 build.  Is there a policy not to use a wait-cursor if not histo is shown?
>  
> Shaping
>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190530/da02cd52/attachment.html>


More information about the Pharo-dev mailing list