>
> Hilaire,
>
> Have you included a method in your BaselineOf that looks like this:
>
>     projectClass
>
>         ^ MetacelloCypressBaselineProject
>
> if not, then what looks like a package-cache problem could be that you
> haven't told Metacello that you are using a metadataless
> filetree/tonel repository.
>
> Metacello has an internal rule to not load Monticello packages of the
> same version, since they are already loaded. However, when using
> metadataless repositories the filetree/tonel Monticello package
> readers typically generate a package name using the author/version
> `-cypress.1`, which make Metacello think that the versions are the
> same and the package is not loaded ... by including the above method
> in your baselineof, Metacello will know to ignore the Monticello
> author/version of the package and always load it....
>
> Of course, because Monticello only installs changed definitions when
> loading a package, "loading the same package over and over again"
> costs a little bit in loading the _definitions_ into the image from
> disk, but doesn't end up compiling any new methods or creating new
> classes ...
>
> Dale
>
> On 1/18/18 6:49 AM, Hilaire wrote:
>> It was a month ago; I don't remember the details but from what I can
>> recover from my memory the scenario was:
>>
>> - From my dev. environment I saved code through Tonel, in the DrGeo
>> used CVS.
>>
>> - When building, I specifically ask the code saved thought Tonel to
>> be installed but the package-cache code version was used instead. It
>> could be out of sync.
>>
>>
>> Le 18/01/2018 à 15:22, Dale Henrichs a écrit :
>>> Hilaire,
>>>
>>> Metacello just uses Monticello for loading and it is Monticello that
>>> is using the package-cache ... if there were a way to turn of the
>>> package-cache for Monticello I don't think that Metacello would know
>>> the difference.
>>>
>>> But, I am curious why you care whether or not package is used?
>>>
>>> Is there a specific problem that you are having?
>>>
>>> Dale
>>