if A.1 depends on B.23
Z.2 depends on B.24
you cannot load A and Z since B.23 and B.24 cannot load together.
So what you do is
If you want to load
A.1 and Z.2
because you load first B.23 or B.24
because you analyzed
But you did not had to change A.1 or Z.2 for that.
You only created a new lineUp
Since other components may want to still load W or A.1 with another B
I let you imagine how this can be the mess with packages depending on
packages depending on package.....
On 20 févr. 06, at 17:44, Samir Saidani wrote:
"stéphane ducasse" <ducasse(a)iam.unibe.ch> writes:
>> Hi Stef,
>> This is what I did : smallwiki-stable is a package with no code and
>> depends from smallwiki-parser which itself depends from
>> smallwiki-kernel. But I don't know why, I miss this point :
> The point is not to have for example smallwiki parser depends on
I must admit that I don't understand at all : so you say that A does
not depend on B anymore, but I don't understand how do you tackle the
dependencies issues with current tools available for squeak
(Monticello I mean ??). And after reading the link you gave me, Avi
seems to say that he follows the same approach than the one reported
on the blog...
I would like to understand the problem.
I've just posted on squeak-dev about that, maybe it could interesting
for the list to dialogue around that...
SmallWiki, Magritte, Pier and Related Tools ...