[Bobs-devel] todo

[Joe z. <jz...@at...>]

Rene,

I saw your additions to the TODO list. I'm getting ready to work on bobs 
tonight and I have my own "todo" list that I want to run by you.

1.    I wasn't clear when I said my makefile "creates the backup data 
directories". It only creates the main directory and the process... 
directories, like this:

<whatever>/bobsdata/
`-- process
    |-- cmd
    |-- mounts
    `-- session

It's my understanding the backup directories (current, incoming, and 
incremental) will be created under "bobsdata", according to config.php. 
These will be created by the httpd process. So in the makefile I need to 
find out who the  httpd user is and create the "bobsdata" directory with 
that user as the owner. I hardcoded the directory name "bobsdata" to 
ensure that "make install" and "make uninstall" won't damage other data. 
So "<whatever>/bobsdata" will be the top of the data directory tree.

2.    As far as autoconf and automake, the user shouldn't need to run 
those after I put "configure" in the CVS. They are only for us 
developers. autoconf reads configure.in and creates configure. automake 
reads Makefile.am and creates Makefile.in. ./configure reads 
Makefile.in, inc/config.php.in and cron/backup.php.in and creates 
Makefile, inc/config.php and cron/backup.php, and does some other 
processing too.

I'm going to put more comments in those files for all our benefit. This 
is the first time I've really used autoconf and automake, so it's a 
learning experience, and it's fun!

3.    I introduced a bug in config.php. A comment is added by 
./configure as the first line and messes up the session header or 
something. That'll be fixed.

4.    I have some more work to do on the makefile, and I think I'll add 
a couple items to the TODO list.

You're replies to my last two emails were very helpful. Some of that's 
on my todo list, and some I'll put on the main TODO list.

Take it easy,
Joe