Ok, I think this case is closed. Having gotten my code out of the image with
Monticello and manual recompile, I can use versionner for upload if and only
if I do it in Pharo6. Likewise, I can use it for download if and only if I
do it in Pharo6. Pharo5 breaks in strange ways on both ends, even with
Thanks for the replies.
With Juraj's help, I figured out the first layer of my problem. I needed to
recompile all the methods after loading the code with Monticello, because
their bytecode was all messed up. Now I can get code out of the image via
plain Monticello. Tests were failing not because o
--- Begin Message ---
Evan wrote:
>If anyone knows how to figure out how to force all the current good code in
>my image into one massive commit, so that other people can check out the
>current, working version, please do not hesitate to let me know.
If you are using mczs, all changes are committ
Hi,
> On May 11, 2017, at 3:55 AM, Juraj Kubelka wrote:
>
> Hi,
>
> I do not understand much you problem. But reading about your commit strategy,
> you can use Gofer object and its push method to sync properly local changes
> to a remote repository. Check Pharo books. There are examples.
>
Hi,
I do not understand much you problem. But reading about your commit strategy,
you can use Gofer object and its push method to sync properly local changes to
a remote repository. Check Pharo books. There are examples.
If you inspect a configuration object, there used to be a GT-Inspector
e
Hello,
I was wondering if there was a resource somewhere that laid out a best
practice for how to manage version control in Pharo. I know *how* to use
Monticello and Versionner, but something about the way I use them
inevitably dooms my efforts to the darkest circles of dependency hell,
where stra
