Hi guys!
I'm having different behaviors when loading metacello configurations using
the configuration directly and using gofer:
This loads well
Gofer it smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
package: 'ConfigurationOfOpenDBXDriver';
load.
(ConfigurationOfOpenDBXDriver project
On 27.04.2014, at 13:55, Guillermo Polito guillermopol...@gmail.com wrote:
Hi guys!
I'm having different behaviors when loading metacello configurations using
the configuration directly and using gofer:
This loads well
Gofer it smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
If I do a normal load it happens the same. The thing is that GoferMetacelloLoad
fetches first some version using the blessing and then using the version
number/symbol.
On Sun, Apr 27, 2014 at 2:05 PM, Max Leske maxle...@gmail.com wrote:
On 27.04.2014, at 13:55, Guillermo Polito
What Guille is saying is that loadVersion: #stable does not imply loading
the #stable blessing. In the Metacello lingo, it implies loading the
#stable symbolic version.
I think the blessing should be deprecated because it is not maintained
reliably (plus it adds yet another level of complexity in
Tudor Girba-2 wrote
I think the blessing should be deprecated because it is not maintained
reliably (plus it adds yet another level of complexity in Metacello
without
a direct significant benefit).
Yes, I don't see what value the blessing provides in light of symbolic
versions... I'd like to
Blessing is an attribute of a particular version ... multiple versions can
have the same blessing, so there is limited utility to blessings ...
personally I find the distinction between #release and #development useful
for blessings with #release declaring that the version will not be changed
