Em 20/06/2010, às 14:45, Luis A. Bastiao Silva escreveu:
>
> 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).
>
> Best Regards,
> --
> Luís A. Bastião Silva
---
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
