Hi Nicolas,

I am very interested in learning more about the .mcm files, for MonticelloConfigurationMaps. I looked at the Monticeelo Configurations Browser but I got lost. Is there are good writeup on how to use it? I am intrigued about establishing dependencies this way to avoid cutting more versions to update the version of the required projects list. A config map for each package, with the dependencies set to the latest version of a dependent app, would be an excellent solution.

Thanks for your assistance!

K, r

On 3/7/20 3:27 PM, Nicolas Cellier wrote:

> Hi Robert,
> there are several possible ways we can split the package and still load the whole thing.
> One is Metacello as indicated by Jakob.
> It shines if wanting to support multiple dialects (Gemstone, Pharo, Squeak), multiple versions of these dialects, and multiple release of our own packages, with slightly different recipes concerning the package assembly.
> It also shines for gathering pacakges from several repositories or handling complex pre-requisites (like FFI, Registers etc...).
>
> Be warned that Pharo users did already tend to fork everything which lies on a squeak* repo when they did use MC.
> With the transition to git, I doubt you maintain anything for Pharo if not for yourself.
> http://smalltalkhub.com/#!/~Cryptography/Cryptography/
> https://github.com/zweidenker/Cryptography
> By the way, I mistakenly uploaded two copies of Blowfish from Mariano Martinez Peck from smalltalkhub to http://www.squeaksource.com/Cryptography This was not necessary because they did not add anything to Blowfish-PaulDeBruicker.10.mcz.
>
> Cuis never used MC, so naturally also tend to republish packages with their own format and own repository on github (mostly traditional .st chunk !).
> https://github.com/garduino/Cuis-Smalltalk-Cryptography
> Maybe https://github.com/KenDickey/Cuis-Smalltalk-Crypto-NaCl can be of interest too.
>
> This is not a critic for Cuis and Pharo, but just to underline that cross-dialect is de facto not the criterion for selecting the packaging techno.
>
> If all packages lie in the same repository and no pre-requisites is required, then there is also a much less powerful, but so much simpler option of using a MonticelloConfigurationMap.
> It is a simple .mcm file listing the sequence of MC packages and version to load.
> Packages are loaded in the order prescribed by the .mcm, and it's possible to load latest versions (highest version numbers).
> There are tools in image for constructing and saving those .mcm
>
> Le sam. 7 mars 2020 à 15:52, Jakob Reschke <forums.jakob at resfarm.de> a écrit :
>
>> Robert via Squeak-dev <squeak-dev at lists.squeakfoundation.org> schrieb am Sa., 7. März 2020, 15:39:
>>
>>> If only Monticello allowed for
>>> dependencies,
>>
>> In fact it does. But it is never used so I suppose some piece is missing.
>>
>> What about Metacello? Most people use it for package dependency management nowadays.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200308/bda01bf1/attachment-0001.html>