Am 20.02.2013 um 11:17 schrieb Esteban Lorenzano <[email protected]>:
> there is a problem with the package definition, I think (PetitXPath != > Petitxpath), and new RPackage cannot detect they are the same... in fact, IMO > that exposes an old PackageInfo bug, not an RPackage problem, so I think the > real solution is to commit a package with a good package name. So, what are the rules. Does the case sensitivity also reflect in method extensions? Meaning do I need to call the extension *petitXPath or even *PetitXPath? > Also, it does not looks like you have the lastest image... you should be > seeing something like this: > Yeah, I made the screenshot with an older image. I retried it then with updating the image first. But seeing that the result ist the same made me send the old screenshot. Norbert > <Screen Shot 2013-02-20 at 11.15.07 AM.png> > > > (notice the diff morph has a bar in the middle, also two text label on top). > > > On Feb 20, 2013, at 11:08 AM, Norbert Hartl <[email protected]> wrote: > >> I opened a fresh pharo 2 (#20559) and loaded PetitXPath. Modifying a method >> does not mark the package dirty in monticello browser. And If I press the >> "changes" button I can see >> >> <Bildschirmfoto 2013-02-20 um 11.00.54.png> >> >> That basically shows all the code that is in the package. But from my own >> change I cannot see anything in there. >> >> Norbert >
