[another "me too"] Re: portindex/portindexdb

[Nico Meijer]

Hi Donald,

> Nico - I suggest you try it again tomorrow. I thought I had it fixed 
> yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is 
> again seg faulting for me. Not going into a loop and continuously 
> seg faulting, but bad enough.

After cvsupping my ports tree, running portindex (not portindexdb!) and 
portsdb -u (which gave core dumps) all is well. No more 'bus errors'.

portindex seems like a wonderful tool, so I'm keeping it around.

HTH and good luck... Nico