Le 02/02/2014 17:11, Pharo4Stef a écrit :
Chris
There are several points:
- we will maintain compatibility when filein/out using *
- now I was not aware that the class extensions should be lower case.
They are in the current implementation of RPackage. Normally there is
code to ensure case-
Chris
There are several points:
- we will maintain compatibility when filein/out using *
- now I was not aware that the class extensions should be lower case.
- Pharo should clean the packages because some of the extensions are
for packages not existing anymore
and
2014-01-31 Chris Cunningham :
> You'll undoubtedly run into this several more times - at least you will when
> bringing in older Monticello packages or those created outside of Pharo. Not
> all, but some.
Some, which will be very important probably. Like Seaside, Glorp, etc.
Regards!
On Fri, Jan 31, 2014 at 3:57 AM, Torsten Bergmann wrote:
> Now that Pharo uses real packages beside categories I see some
> lowercase "ghost" packages in Monticello Browser list after loading
> Seaside.
>
> To reproduce just load Seaside using config browser and check in
> Monticello browser.
>
>
On 31 Jan 2014, at 11:57, Torsten Bergmann wrote:
> Now that Pharo uses real packages beside categories I see some
> lowercase "ghost" packages in Monticello Browser list after loading Seaside.
>
> To reproduce just load Seaside using config browser and check in
> Monticello browser.
>
>
>
Now that Pharo uses real packages beside categories I see some
lowercase "ghost" packages in Monticello Browser list after loading Seaside.
To reproduce just load Seaside using config browser and check in
Monticello browser.
I guess this is coming from methods in lowercase extension
categories
