[mnet-devel] library layout

[icepick at icepick.info]

On Mon, Mar 24, 2003 at 06:16:18AM -0500, Zooko wrote:
> 
> Myers:
> 
> I think on IRC you said that you wanted to put all source code into one CVS 
> module.  I'm open to that possibility.
> 
> I originally put everything that could be used separately (egtp, pyutil, 
> libbase32, ...) into separate sf.net projects because I envisioned telling 
> someone "You could use EGTP for that.", and them saying "No way am I going to 
> look at the Mnet source code just because I want EGTP.".
> 
> Also, I didn't realize that having things separate would make building and 
> installing harder.
> 
> So if it would help, we could put them all together and if the imaginary 
> conversation above ever comes to pass then we can break them out again.  :-)

It's not that it makes it harder.  It's just I don't really find pulling 4
(mnet, egtp, pyutil, libbase32... soon to add fec somewhere) modules out of
CVS elegant.  Nor maintaining 4 different build systems.  ./setup.py
download still feel fragile, because there are a lot of moving parts inside,
and if one goes wrong the user doesn't know what's broken.

This would get things a lot closer to the 2 minute max setup time for a
builder/new developer that I would like.

Also egtp/libbase32/pyutil would all live in dirs right under mnet_new/ and
be nice little python modules that anyone could copy out of there in a flash
and use.

So... unless someone says otherwise I'll "make it so".

icepick


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel