But isn't that a bit... weird to use cache to move data from one image to
another? I would expect cache to be just a cache even if in reality it is
just a regular repository.
On Fri, Jul 25, 2014 at 12:48 AM, Norbert Hartl wrote:
>
> Am 24.07.2014 um 23:43 schrieb Stephan Eggermont :
>
> > If y
Am 24.07.2014 um 23:43 schrieb Stephan Eggermont :
> If you use a shared package cache, you should be aware of two potential
> issues:
> - directories with a large number of files can get slow;
I don't think that this is an issue with todays filesystems. If you want to
cleanup a package-cache
If you use a shared package cache, you should be aware of two potential issues:
- directories with a large number of files can get slow;
- Metacello configurations might load different versions of packages than you'd
expect
Stephan
Thank you all so much!
This is is exactly what I was looking for and a lot more.
On Thu, Jul 24, 2014 at 6:29 PM, Ben Coman wrote:
> Sven Van Caekenberghe 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 streng
Sven Van Caekenberghe 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 be
On Thu, Jul 24, 2014 at 3:27 PM, Tudor Girba wrote:
> 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.
I agree I do the same. Jenkins and the Pharo Launch
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
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 you
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
