Smalltalk › Pharo › Pharo Smalltalk Users

Problems with Categories, PackageInfo and RPackage

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

MartinW

Problems with Categories, PackageInfo and RPackage

Hi,
i am using the Spy framework in Pharo 2.0 which makes use of PackageInfo. It seems PackageInfo is not updated properly:

Try this:
PackageInfo allPackages size. 562
RPackageOrganizer default packages size. 540
SystemOrganization categories size. 476

Object subclass: #MyClass
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: 'MyNewCategory'

PackageInfo allPackages size. 562
RPackageOrganizer default packages size. 541
SystemOrganization categories size. 477

And why are the numbers of PackageInfo packages, RPackage packages and categories so different in the first place?

(I did file a bug for this: https://pharo.fogbugz.com/f/cases/11653)

Now the question is, what can i do?
1) Hope someone fixes the PackageInfo updating?
2) Is there a guide for how to move something from using PackageInfo to RPackage? So i could try to change the relevant pieces in Spy?

M.

Stéphane Ducasse

Re: Problems with Categories, PackageInfo and RPackage

Because package info is bogus!

Stef
On Sep 22, 2013, at 1:24 PM, MartinW <[hidden email]> wrote:

> Hi,
> i am using the Spy framework in Pharo 2.0 which makes use of PackageInfo. It
> seems PackageInfo is not updated properly:
>
> Try this:
> PackageInfo allPackages size. 562
> RPackageOrganizer default packages size. 540
> SystemOrganization categories size. 476
>
> Object subclass: #MyClass
> instanceVariableNames: ''
> classVariableNames: ''
> poolDictionaries: ''
> category: 'MyNewCategory'
>
> PackageInfo allPackages size. 562
> RPackageOrganizer default packages size. 541
> SystemOrganization categories size. 477
>
> And why are the numbers of PackageInfo packages, RPackage packages and
> categories so different in the first place?
>
> (I did file a bug for this: https://pharo.fogbugz.com/f/cases/11653)
>
> Now the question is, what can i do?
> 1) Hope someone fixes the PackageInfo updating?
> 2) Is there a guide for how to move something from using PackageInfo to
> RPackage? So i could try to change the relevant pieces in Spy?
>
> M.
>
>
>
> --
> View this message in context: http://forum.world.st/Problems-with-Categories-PackageInfo-and-RPackage-tp4709620.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>

MartinW

Re: Problems with Categories, PackageInfo and RPackage

I believe you, of course :)
Now where would i look to learn enough about both systems to migrate some tool/framework from PackageInfo to RPackage?

Stéphane Ducasse wrote

Because package info is bogus!

> Now the question is, what can i do?
> 1) Hope someone fixes the PackageInfo updating?
> 2) Is there a guide for how to move something from using PackageInfo to
> RPackage? So i could try to change the relevant pieces in Spy?

Stéphane Ducasse

Re: Problems with Categories, PackageInfo and RPackage

I do not get why Spy relies on PackageInfo
may be just to scope installation. So you should be able to ask RPackageOrganizer for the classes associate to a package.

Stef

On Sep 22, 2013, at 3:38 PM, MartinW <[hidden email]> wrote:

> I believe you, of course :)
> Now where would i look to learn enough about both systems to migrate some
> tool/framework from PackageInfo to RPackage?
>
>
> Stéphane Ducasse wrote
>> Because package info is bogus!
>>
>>> Now the question is, what can i do?
>>> 1) Hope someone fixes the PackageInfo updating?
>>> 2) Is there a guide for how to move something from using PackageInfo to
>>> RPackage? So i could try to change the relevant pieces in Spy?
>
>
>
>
>
> --
> View this message in context: http://forum.world.st/Problems-with-Categories-PackageInfo-and-RPackage-tp4709620p4709632.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>

EstebanLM

Re: Problems with Categories, PackageInfo and RPackage

In reply to this post by Stéphane Ducasse

not just bogus, it is also deprecated.
is there just because is hard to remove it... but no new functionality should be implemented on it (it will not be there in 3.0, also, since it was deprecated in 2.0).

Esteban

On Sep 22, 2013, at 1:45 PM, Stéphane Ducasse <[hidden email]> wrote:

> Because package info is bogus!
>
> Stef
> On Sep 22, 2013, at 1:24 PM, MartinW <[hidden email]> wrote:
>
>> Hi,
>> i am using the Spy framework in Pharo 2.0 which makes use of PackageInfo. It
>> seems PackageInfo is not updated properly:
>>
>> Try this:
>> PackageInfo allPackages size. 562
>> RPackageOrganizer default packages size. 540
>> SystemOrganization categories size. 476
>>
>> Object subclass: #MyClass
>> instanceVariableNames: ''
>> classVariableNames: ''
>> poolDictionaries: ''
>> category: 'MyNewCategory'
>>
>> PackageInfo allPackages size. 562
>> RPackageOrganizer default packages size. 541
>> SystemOrganization categories size. 477
>>
>> And why are the numbers of PackageInfo packages, RPackage packages and
>> categories so different in the first place?
>>
>> (I did file a bug for this: https://pharo.fogbugz.com/f/cases/11653)
>>
>> Now the question is, what can i do?
>> 1) Hope someone fixes the PackageInfo updating?
>> 2) Is there a guide for how to move something from using PackageInfo to
>> RPackage? So i could try to change the relevant pieces in Spy?
>>
>> M.
>>
>>
>>
>> --
>> View this message in context: http://forum.world.st/Problems-with-Categories-PackageInfo-and-RPackage-tp4709620.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>
>
>