[Pharo-project] RPackage and Monticello are dependent on each other
Hi, we have small dependency problem. The RPackage is currently dependent on Monticello and Monticello is dependent on RPackage. This makes them unable to load them to Pharo Kernel. I suppose this will fix the worst: MCPackage organization renameCategory: '*RPackage-Core' toBe: '*RPackage-SystemIntegration'. I will open an issue. Cheers, -- Pavel
we have small dependency problem. The RPackage is currently dependent on Monticello and Monticello is dependent on RPackage. This makes them unable to load them to Pharo Kernel.
I think that this is just a problem that we should fix once we get rid of packageInfo and friends.
I suppose this will fix the worst: MCPackage organization renameCategory: '*RPackage-Core' toBe: '*RPackage-SystemIntegration'.
I do not get that one. Can you explain the root of the cycle?
I will open an issue.
Cheers, -- Pavel
On Sun, May 6, 2012 at 12:57 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
we have small dependency problem. The RPackage is currently dependent on
Monticello and Monticello is dependent on RPackage. This makes them unable to load them to Pharo Kernel.
I think that this is just a problem that we should fix once we get rid of packageInfo and friends.
I suppose this will fix the worst: MCPackage organization renameCategory: '*RPackage-Core' toBe: '*RPackage-SystemIntegration'.
I do not get that one. Can you explain the root of the cycle?
RPackage-Core contains extension of MCPackage class and Monticello initialization is dependent on Ring. This way we can load packages in order RPackage-Core, Monticello, RPackage-SystemIntegration. -- Pavel
I will open an issue.
Cheers, -- Pavel
participants (2)
-
Pavel Krivanek -
Stéphane Ducasse