Hi,

I change my image at least once per day. Every single day. I have automatic
jobs that create an up to date images the way I want them, and I simply
take that one whenever I feel like it.

This helps me push my code to a repository, and have any setup easily
reconstruct-able. If a piece of code does not make it in even a playground
repository, it is probably not worth having it around anyway.

For me, it is a matter of principle.

Cheers,
Doru




On Thu, Jul 24, 2014 at 3:17 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote:

> Hi Peter,
>
> I and I guess most people, keep their working image for days to weeks.
> After all, it is one of the main strengths to have a persistent environment
> containing all you customisations, all code you loaded, your workspaces, in
> essence, your world.
>
> That being said, you should keep all your important code in an MC
> repository (at least in the package-cache, but better in a real repository,
> maybe a private one). That way you know your code will survive an image
> crash.
>
> When and if you want to upgrade, you can now do so. You have to decide if
> the trouble is worth it. I always keep the old images, just in case.
>
> HTH,
>
> Sven
>
> PS: You can save workspaces to files, or use ScriptManager for multiple
> ones. There also exists various solutions to move preferences and/or
> settings around, YMMV.
>
> On 24 Jul 2014, at 14:58, Peter Uhnák <i.uh...@gmail.com> wrote:
>
> > Having ~month old pharo image I was wondering what is the recommended
> way of updating it. Do I just delete everything and download a fresh one
> every so often (daily?), do I load new changes through Monticello? Does
> that upgrade the VM though?
> > If the former what about local code I wrote but I don't want to loose or
> haven't completely finished? Is it possible to export workspace content and
> load it into fresh image?
> > Do I just create local repository and commit there and once I am
> satisfied with the results I push them up (to STHub/wherever)? Or should I
> always push to remote repo even if the commits break the package (I would
> assume that should be semi-guarded by creating ConfigurationOfMyProject)? I
> am used to Git and I still can't wrap my head around this Monticello thing.
> :(
> >
> > Thanks,
> > Peter
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Reply via email to