Re: [mdbtools-dev] Many patches, is that project dead? Fork?

Hi Thomas,

Help with getting patches applied is greatly appreciated.  I'm hoping
to be more active in the near term.  I've had some other projects
taking precedence over the past year.  Like I mentioned in the last
email, I have a github repo, let me know if want to clone or whatever
and I can merge back from you or whatever you think works best.

Somebody mentioned write support.  Where I last left it was I was
working on the mdb-import utility which will allow a CSV file to be
imported into an existing table.  There is a gap in my understanding
of the allocation map which allowed me to add rows to an existing
page, but rows on newly allocated pages didn't appear when read with
Access.  I just need to find a few hours of uninterrupted time to play
and figure out what's going on there and things should start moving.


Brian

2010/6/16 Thomas Adam <[email protected]>:
> On Wed, Jun 16, 2010 at 02:06:26PM +0100, Tim Retout wrote:
>> On 16 June 2010 13:10, Brian Bruns <[email protected]> wrote:
>> > The project has been kind of dead.  I'm hoping to find some time to
>> > get back to it real soon now.  In particular I'd be happy to look at
>> > the patches and apply them to the tree.  Actually, I'd love to get out
>> > of CVS and into something a little more modern such as git, truth be
>> > told.
>>
>> [Adding Thomas Adam to CC.]
>>
>> Just last week, I've been talking to Thomas about exactly this issue.
>> We'd like to set up a git repository and start to fix some of the more
>> obvious bugs.  Give it another week and we probably will. :)  mdbtools
>> is still a popular package (depended upon by openoffice.org-base).
>
> Yes -- I took a look at the repo on collab-maint, which is what the mdbtools
> debian package is derived from, although I would suggest that we take the
> latest CVS code from sourceforge and put it on github.
>
> I've already done this on my workstation, actually.  I suppose I could just
> go ahead and publish that to my github account [0] this evening -- probably
> makes life a bit easier, rather than vying for different repositories others
> have created.  :)
>
> I spent a couple of hours this week looking over the BTS for mdbtools as
> well as the code in general.  I am happy to say that most of the bugs, and
> perhaps more importantly, my own observations initially lend themselves well
> to quite a simple clean-up process of the code -- I've already identified, I
> think, about four or five areas where segfaults are likely to happen.  :)
>
> So... I'd be more than happy to do two things:
>
> 1. Shove the repository on github.
> 2. Push a bunch of patches out to fix segfaults.
> 3. Review patches.
>
> Although point 3, is something I'd like others to also do -- especially
> those on the PTS for mdbtools.
>
> I hope that's not sounding too push -- if it is, tell me to back off.  :)
>
> Brian -- I appreciate this might be treading on your toes somewhat, but how
> active do you think you'll be to maintain mdbtools from this point onwards?
>
> Kindly,
>
> -- Thomas Adam
>
> [0] http://www.github.com/ThomasAdam
>

------------------------------------------------------------------------------
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