[Seaside] Problem upgrading seaside from an existing image (Pharo
#14438 and Seaside 3.0)
diego.lont at delware.nl
Fri Sep 6 10:54:02 UTC 2013
I realize I should have sent you this reply before.
First thing I always check if I run into trouble is whether Metacello can determine what packages to load. If not, I know the problem lies in the configurations, if it can determine, it allows me to load the packages manually in the same order as metacello.
And I always forget what method to call. I have to look it up. Below here only traverses the configuration itself, but is a good first test.
(ConfigurationOfSeaside3 project version: #stable) expandToLoadableSpecNames: #( default )
On Sep 6, 2013, at 12:11 PM, Dave wrote:
> Stephan Eggermont wrote
>> Ok, I wasn't clear.
>> I was looking at the packages downloaded to the package cache
>> seaside mailing list
>> seaside at .squeakfoundation
> I see, but in the package cache you can have several versions of a package,
> only monticello shows the right version that image is using. Am I wrong?
> View this message in context: http://forum.world.st/Problem-upgrading-seaside-from-an-existing-image-Pharo-14438-and-Seaside-3-0-tp4706594p4706866.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside