[mnet-devel] Getting back up to speed (gettting it to build)

rob kinninmont lists+mnet-devel at evilrob.com
Thu May 15 18:10:21 BST 2003


On Thu, May 15, 2003 at 08:06:20AM -0400, Zooko wrote:
> 
> > > cvsinstall.sh wont help, its a _new problem.
> > 
> > right. I guess I have some lingering memory of when I started playing with _new
> 
> Whoa -- you're using _new?

Heh. Er, yeah. I didn't realise that would be surprising...

> I think we need to talk about this.  I consider the _new branch to be 
> completely experimental.  For example, yesterday I made a commit that cvs 
> remove'd a whole bunch of files from _new -- files that _new can't work 
> without, but that won't be needed once I finish the new emergent network 
> named "ent".

Hmm. I hadn't realised that it was in that sort of flux.  I guess that's the
price I pay for not paying attention ;-)

> I think you should just use v0.6.1.  For starters, it will compile right out 
> of the box on OSX.
> 
> However, if for some reason you don't want to do that, then we need to agree 
> on a semi-stable branch within _new so that changes like that one I just 
> committed don't interfere with your work.

The good news is that 0.6.1 does indeed build on my mac. :-)

The reason I'm looking at _new is that I'm curious about the whole xmlrpc/
mnetcli stuff.  I'd like to figure out/learn/wrap my head around the issues
for a variety of reasons. (e.g. xmlrpc looks like a useful tech to have a
bit of experience with) Perhaps moreover though, I'm curious about having the
broker 'headless' (i.e. a daemon) and the UI being a distinct process.

My guess is that's it's not worth trying to retrofit any of that stuff into 0.6
so I'd be interested in getting _new running - though given the current flux
I don't feel a strong need to be at the bleeding edge.  (As an aside it'd be
nice to be more involved in the current edge of mnet stuff, but I don't 
imagine I'll have time to do that for a while, at least until my life settles
down a bit more...)

so I guess the best plan of action (since I don't need to be especially
current yet) might be just for me to check out based on a date when things
worked, rather than worrying you guys with a branch and stuff just for me.

Any suggestions of a date that's a good candidate?

On Thursday, May 15, 2003, at 05:08 AM, Zooko wrote:

>> and a quick look at cvsweb suggests that blockwrangler went away 
>> intentionally, so I guess there's something stale in startup.py... ?
>
> Yep, this was the stuff I removed yesterday.
>
> We had a conversation about it on IRC, and Tschechow, the Guardian of the Purity 
> of the _new Branch, agreed to merge the ent work.  (Although perhaps he didn't 
> realize that I was going to break it now and fix it later.)

heh. note to self: try and keep up with the IRC discussion...

> Sorry that I didn't think of the possibility that you were going to try it.

No worries.

Hey, I'm sorry I stumbled in without warning, then asking for help getting stuff
to work....

cheers,
rob

--
rob kinninmont

"War doesn't determine who's right. War determines who's left."


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel




More information about the Mnet-devel mailing list