On 31/05/2015 13:34, Yuriy Tymchuk wrote:
On 31 May 2015, at 13:29, stepharo <[email protected]
<mailto:[email protected]>> wrote:
Hi,
this is an observation on usage of Metacello. I guess that metacello
is too complicated to be used. For example I was using the `jenkins`
version of Woden configuration, but now it’s broken.
How?
And when you look at the Woden repo[1] it says that the way to load
it is:
Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL';
package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at:
#ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new
smalltalkhubUser: 'Pharo' project: 'OSWindow'; package:
'ConfigurationOfOSWindow'; load. (Smalltalk at:
#ConfigurationOfOSWindow) loadBleedingEdge. Gofer new
smalltalkhubUser: 'ronsaldo' project: 'Woden'; package:
'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden)
loadBleedingEdge
Maybe instead of depending on the configuration of Woden, and saying
that to load my project, people should just use a stable version of
my configuration, I should copy the script from Woden repo, add some
more lines to load the other projects I depend on and ask people to
run a half page script in order to use my tools?
What do you think? it looks like an easier solution.
I do not understand your problem.
I know that jb produced a new configuration for Woden.
And it should work.
But it doesn’t ;). The script loads everything, while the
configuration says: "Error: Name not found: WithOpenGLAndExamples”.
It's not broken it's just a bug related to configuration present by
default in the image, you have to unload the oswindow configuration first...
MCPackageLoader unloadPackage: (MCPackage named: 'ConfigurationOfOSWindow')
Every project should have a configuration.
But it should be a responsibility of the owner, not JB…
Stef
