>>
>>>
>>> 4 - Zion got it's own dir. In order to use it inside network-scanner we'll
>>> be using an svn:externals to link it to the zion's trunk. That's better
>>> because zion can be released as an independent project.
>>>
>>> Could you give more details about that? Actually zion trunk have umit
>>> embedded. Why should zion include network-scanner as svn:externals?
>>
>> It shouldn't feature Umit, actually. Zion is meant to be distributed as a
>> command line and lib, and the network scanner should import the zion lib and
>> make use of it in its interface. It does fetaure Umit now, but that's for
>> the sake of adapting the interface for integrating Zion. Thinking about
>> this, a branch for integrating Zion should feature network scanner's trunk,
>> not zion's. And zion's trunk should feature only zion related code, and use
>> svn: externals to link other modules it might need (like umit.core).
>>
>> Should Network Scanner include zion as svn:externals? Why are you trying do
>> oposite?
>> It's like zion use umpa as svn:externals.
>
> Aren't we integrating Zion into Network Scanner? Aren't we going to
> distribute Zion as an independent module for those who wants to use it
> somewhere else without our Network Scanner?
> Therefore, it needs a separate repository, because it is an independent
> project, but, as we use it with Network Scanner then we need it inside the
> reach of Network Scanner's code. That's why I suggested that we should use
> svn:externals to link zion's modules inside Network Scanner repository.
>
>
> Yes! I agree! But you didn't say that in previous emails.
> Actually zion trunk is wrong. It uses Network Scanner.
>
> - zion trunk should include just zion (and may be clann, not sure).
> - Network Scanner can include svn:externals to umit.zion
>
> It's seems a reasonable approach. What you think about that?
Yes, I think that's the way we should do this. But I think that now it is
Diogo's dutty to separate these stuffs as he develops his proposal. I'm afraid
that too many hands on it now could affect his work. Let's just leave this Zion
issue for Diogo to set alone, and in case he needs any help he can always come
back to me or our mailing list for help. Is that fine for you, Diogo? I just
don't want to mess with what you at least have working now.
Kind Regards,
---
Adriano Monteiro Marques
http://www.thoughtspad.com
http://www.umitproject.org
http://blog.umitproject.org
http://www.pythonbenelux.org
"Don't stay in bed, unless you can make money in bed." - George Burns
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel
