Re: No Gnus feature request: simpler file structure for synching

["Steven E. Harris" <seh@panix.com>]

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

John Owens <jowens@ucdavis.edu> writes:

> Unfortunately, the file structure for gnus is fairly complex. Kai
> points out that he synchs the following files to move state:

I agree that the set of files is daunting. In particular, the split
between having a few files littered in the home directory versus
entire trees of relevant files makes using rsync difficult. It would
be much easier if all settings were rooted under one directory, and
better partitioned therein by server.

After fiddling around with rsync for an entire day trying to
understand inclusion and exclusion lists, I still wound up finding
success only by running it twice: once to exchange a few files in my
home directory, again to exchange most of the files under the main
Gnus directory. Find the program attached, called 'gnusync.'


[-- Attachment #2: gnusync --]
[-- Type: text/plain, Size: 548 bytes --]

#!/bin/sh

CMD='rsync -e ssh -lptD -vuzb --exclude='*~''
REMOTE=Panix:~/temp/sync/gnus

HOME_FILES=".newsrc .newsrc.eld .bbdb .diary"
NEWS_DIR="$HOME/doc/news"


OP=$1

case $OP in
get)
    shift 1
    cd $HOME
    $CMD -r $* $REMOTE/home/ .

    cd $NEWS_DIR
    $CMD -r $* $REMOTE/news/ .
    ;;

put)
    shift 1
    cd $HOME
    $CMD $* $HOME_FILES $REMOTE/home/

    cd $NEWS_DIR
    $CMD -r --delete \
    --exclude='/agent/' \
    $* . $REMOTE/news/
    ;;

*)
    PROG=`basename $0`
    echo "Usage: $PROG (get|put)"
    exit 1
    ;;
esac

[-- Attachment #3: Type: text/plain, Size: 22 bytes --]


-- 
Steven E. Harris