Metacello cannot download the latest zip of a github repo if a zip already exists from a previous commit
So it looks like that when I do Metacello new baseline: 'ChronosManager'; repository: 'github://kilon/ChronosManager'; load and I have ChronosManager already installed via the same command previously , if the repo has changed in the mean time , it wont get the latest zip from github and instead will use the existing zip to overwrite my image (Not cool at all). Obviously a bug ?
On 12/13/15 6:28 AM, Dimitris Chloupis wrote:
So it looks like that when I do
Metacello new baseline: 'ChronosManager'; repository: 'github://kilon/ChronosManager'; load
and I have ChronosManager already installed via the same command previously , if the repo has changed in the mean time , it wont get the latest zip from github and instead will use the existing zip to overwrite my image (Not cool at all).
Obviously a bug ? No it is intended behavior ... to avoid downloading the entire zipped repository everytime you reference a project (whether or not there were changes up on github), the cache is not flushed unless you do a `get` command as follows:
Metacello new baseline: 'ChronosManager'; repository: 'github://kilon/ChronosManager'; get; load (you probably need to use the latest version of Metacello, as well) I see that I haven't documented this feature and that is "not cool at all" .... most of the code and documentation was written about 3 years ago, so users have finally caught up with me and it's time to update the docs:) Dale [1] https://github.com/dalehenrich/metacello-work/issues/380
Thanks Dale , good news it works on Pharo 5 :) Is there a way to delete the previous data = delete the previous zip file and all its decompressed folders / files ? I can do it manually but I was wondering if metacello offers anything similar. On Mon, Dec 14, 2015 at 3:19 AM Dale Henrichs < dale.henrichs@gemtalksystems.com> wrote:
On 12/13/15 6:28 AM, Dimitris Chloupis wrote:
So it looks like that when I do
Metacello new baseline: 'ChronosManager'; repository: 'github://kilon/ChronosManager'; load
and I have ChronosManager already installed via the same command previously , if the repo has changed in the mean time , it wont get the latest zip from github and instead will use the existing zip to overwrite my image (Not cool at all).
Obviously a bug ? No it is intended behavior ... to avoid downloading the entire zipped repository everytime you reference a project (whether or not there were changes up on github), the cache is not flushed unless you do a `get` command as follows:
Metacello new baseline: 'ChronosManager'; repository: 'github://kilon/ChronosManager'; get; load
(you probably need to use the latest version of Metacello, as well)
I see that I haven't documented this feature and that is "not cool at all" .... most of the code and documentation was written about 3 years ago, so users have finally caught up with me and it's time to update the docs:)
Dale
[1] https://github.com/dalehenrich/metacello-work/issues/380
On 12/13/2015 09:59 PM, Dimitris Chloupis wrote:
Thanks Dale , good news it works on Pharo 5 :)
Is there a way to delete the previous data = delete the previous zip file and all its decompressed folders / files ? I can do it manually but I was wondering if metacello offers anything similar.
You can delete the github-cache directory anytime you want, and the cache should be rebuilt the next time you do a build ... Metacello itself does not offer a service for deleting the cache directory ... Dale
Ok thanks Dale that's all I wanted to know On Mon, 14 Dec 2015 at 19:54, Dale Henrichs < dale.henrichs@gemtalksystems.com> wrote:
On 12/13/2015 09:59 PM, Dimitris Chloupis wrote:
Thanks Dale , good news it works on Pharo 5 :)
Is there a way to delete the previous data = delete the previous zip file and all its decompressed folders / files ? I can do it manually but I was wondering if metacello offers anything similar.
You can delete the github-cache directory anytime you want, and the cache should be rebuilt the next time you do a build ... Metacello itself does not offer a service for deleting the cache directory ...
Dale
participants (2)
-
Dale Henrichs -
Dimitris Chloupis