On 2/18/17 7:32 AM, Hilaire wrote:
Dale,
May be you don't want to waste anymore time on that. Thanks for your
effort. I got a way to get Voyage installed in my development image.
Well I am still curious why you are having trouble ...
Not sure what wrong, because something is wrong[1], but I got the things
installed, first update to Seaside, which break when upgrading the
Seaside installed from the configuration browser, fix the seaside broken
installation, then install Voyage which went fine. Did not test Voyage
is working though.
I am glad that you've found a formula ... But I am still curious ...
I've looked at the configurations and I don't see anything odd ... as
you have observed, without Seaside pre-installed Voyage/Magritte will
not cause Seaside to get loaded ... In addition if just Seaside is
installed, there is no reason I can see that Voyage/Magritte would cause
Seaside to be updated ... UNLESS, Magritte-Seaside is installed.
Below you mention that Magritte3 from ConfigurationBrowser is installing
Seaside update as well, and that would be consistent with the
Magritte-Seaside package being loaded for some reason ...
I would be interested to see how you loaded Seaside in the first place.
Were you loading Magritte first? I am wondering about how
Magritte-Seaside package is getting installed ...
I have some ideas about better ways to solve your installation problem,
but I've run out of time tonight ... I will send more mail tomorrow...
Dale
Hilaire
[1]The Pharo4 configuration browser's Magritte3 is installing Seaside
update, this should NOT happen.
Now image comes with a Configuration Browser, if I understand correctly
its intend, an user is expected those configurations to work happily
together, but it looks like not, some configurations will request update
breaking package previously installed from this configuration browser.
May be it is more a policy problem on the quality of the configuration
than a tool problem, a lot can be learn from Debian packaging. For
example Debian stable is released only when quality is ok, don't know
the details but they don't like to rush for release and people complain
new stable release take too much time to emerge, the price for quality?
For me Pharo fells too fuzzy, and it makes me very sceptical for
reliability; may be not nice to write and to read but it is how I fell.
I may be biased and I don't mean bad to anyone writing this, I know how
quality is hard to achieve and Pharo teams did great endeavour in many
aspects.
Le 17/02/2017 à 22:15, Dale Henrichs a écrit :
Again, thanks for detailed info ...
The fact that you loaded Seaside3.1.x is good enough for my purposes
.. the fact that Seaside3.2 is getting installed implies that there is a
hard dependency on Seaside in one of the projects (Magritte3 perhaps?)
... odd that ConfigurationOfSeaside3 wasn't downloaded this time around
--- Can you get the package version of ConfigurationOfSeaside3 that's in
the image after the `Metacello new` loads?... I'll have to dive into the
configurations now ...
