Did you read the chapter on Metacello in deep into Pharo?
in essence you create a class where you express dependencies to other
projects and packages.
Have a look at the configuration of Soup for example
Object subclass: #ConfigurationOfSoup
instanceVariableNames: 'project'
classVariableNames: 'LastVersionLoad'
package: 'ConfigurationOfSoup'
ConfigurationOfSoup >> baseline19: spec
<version: '1.9-baseline'>
spec for: #'common' do: [
spec blessing: #'baseline'.
spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'.
spec project: 'XMLParser' with: [
spec
className: #ConfigurationOfXMLParser;
versionString: #'stable';
repository:
'http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main' ].
spec
package: 'Soup-Core' with: [
spec requires: #('XMLParser' ). ];
package: 'Soup-Zinc' with: [
spec requires: #('Soup-Core' ). ];
package: 'Soup-XPath' with: [
spec requires: #('Soup-Core' ). ];
package: 'Soup-Help' with: [
spec requires: #('Soup-Core' ). ];
package: 'Soup-Tests-Core' with: [
spec requires: #('Soup-Core' ). ];
package: #'Soup-Tools' with: [
spec requires: #('Soup-Core' 'Soup-Zinc'
'Soup-XPath' 'Soup-Help' ). ].
].
On Sun, Dec 17, 2017 at 6:53 AM, Eno <tgk...@gmail.com> wrote:
> Sure, it's a great news that the leader could give me a hand.
>
> I came from Dolphin, not acquainted with pharo configuration, though I knew
> a lot that it could automize the loading and update.
>
> It depended upon Magritte3, Sandstone, and my packages.
>
> The store directory need to be changed in other's new image, currently, I
> set it fixed inside the method, MacOSResolver>>store,
> WindowsResolver>>store.
>
> On new installed image while running up via wordmenu, a new db file need to
> be created from the tool icon.
>
>
> Thanks.
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
