Le 08/04/2015 19:41, Johan Brichau a écrit :
Hi all,
Over the last week, I started working with Pharo4, mostly to make Seaside work
cleanly.
On several occasions, I had severe issues with the package management:
- methods that were changed in a class were not recorded as ‘changed’ in
monticello and were absent from the published package
- versions of methods disappeared (i.e. no longer accessible in the version
history of a method)
- looking at the ‘changed’ in Monticello showed all code of the package as
changed (though only a single method has changed).
This makes working with Pharo4 extremely problematic. I cannot trust the source
code packaging/publishing and merging anymore.
I cannot discern a scenario that leads to these issues but I do have an image
right now where I only changed a single method and the entire package shows up
as ‘changed’.
Anyone experience similar issues?
Hi Johan,
Yuriy's issue with Komitter and GitFileTree is the same problem.
I'd really need to have the ability to reproduce that. Or have access to
an image where it has happened. I'd really like to inspect the relevant
package working copy, its ancestry and the associated RPackage.
Thierry
