[mnet-devel] Mnet build questions.

[Zooko]

> The mnet_new setup stuff doesn't deal with pybsddb directly, it simply tells one to install v3.3.0.  The twist is that it needs to be a _Patched_ version of 3.3.0, wh
> ich you won't get if you e.g. install from an rpm.
> 
> I'll have a go at installing a patched version on my linux box.  

Myers is responsible for the mnet_new build process, and I would be surprised 
if he allowed it to be in that awful state where you need to patch your 
pybsddb!  I'm pretty sure we just use the pybsddb from Debian nowadays.

> > Your second problem is something that has been fixed in newer versions of 
> > mnet_new.
> 
> Hmm.  Do you know off-hand what/where the fix is?  If it's a small fix, I'd probably like to apply it retroactively to my May12 snapshot.

Myers is responsible for this part, also.  He and Arno worked for a long time 
to get the FEC code to build on w32, and now it does.  Try something like:

cvs log `find . -iname '*fec*.py'` `find . -iname '*fec*.c'`

?

> I'm not going to argue with the wisdom of that as a coding/engineering 
> practice... but I really don't think it's necessary at the moment.

Well, I'm not certain (and according to IRC chatter, neither is Tschechow 
certain) that the May 12 snapshot + fixes will be able to upload and download.

On the other hand, current HEAD can definitely not upload and download.

The only version that I am certain will upload and download is the v0.6 branch.

Regards,

Zooko

http://zooko.com/
         ^-- under re-construction: some new stuff, some broken links



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel