Hilaire
A BaselineOf is the equivalent in better to a ConifgurationOf
The key benefit is that you just specify a kind of ConfigurationOf
baseline and you are done
No need to express manually versions.
With a baseline you can get branches, a specific hash....
So you have all the power but with less burden.
Side: I do not like the git API but I coding with git and the branches
are really really nice.
You can have multiple versions
- release
- dev
- dev + a features and simply manage it
So git is really a plus
With Iceberg 20, you will also be able to manage external ressources
(icons, text...)
and this is cool
Stef
---------- Forwarded message ----------
From: Hilaire <hila...@drgeo.eu>
Date: Mon, Apr 2, 2018 at 3:46 PM
Subject: Re: [Pharo-users] unsolicited package-cache use
To: pharo-users@lists.pharo.org
Hi Dale,
Sorry to reply very lately to your help email, I am getting slow on
Pharo those those days.
I am afraid to be a bit out of sync: what is a BaselineOf? I only have
a ConfigurationOfDrGeo and baseline methods into.
Hilaire
Le 18/01/2018 à 16:10, Dale Henrichs a écrit :
>
>
> 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
>>
>>
--
Dr. Geo
http://drgeo.eu
