Alternatively you could use the ./scripts/switch_submodules_to_head_and_clean script; it will do this task for you... Tim

David C. Rankin Where is the./scripts/switch_submodules_to_head_and_clean script--that I can customize for my personal use--located? The only copy of this script that I have found so far is part of the download itself. I assumed that the script resides in the repository and that my script calls it from the repository location. Keith On Wed, Feb 29, 2012 at 9:04 AM, David C. Rankin <drankinatty(a)suddenlinkmail.com> wrote:

Thanks Darrell The only possible problem that I see is that everytime I have tried to run the startup script in the past, and there was ANYTHING in: zz_src_trinity_git It would abort with an error: "Directory not empty" type of message. I will try the above and get back to you with the results. Keith On Wed, Feb 29, 2012 at 2:20 PM, Darrell Anderson <humanreadable(a)yahoo.com> wrote:

Hmm. I never used a password until very recently when I was granted commit access. Up until then I always connected anonymously. I wonder whether entering a password just once has an effect that prevents anonymous connections. If I recall correctly, when I first connected a few days after the GIT announcement in December, I manually created the local GIT directory (mkdir), did a cd to that directory and manually ran git clone --- without a script. Like this, but all manually: mkdir -p /home/public/builds/slackware/trinity/zz_src_trinity_git cd /home/public/builds/slackware/trinity git clone --recursive http://scm.trinitydesktop.org/scm/git/tde zz_src_trinity_git Notice I did a cd to the parent directory of $GIT_DIR (zz_src_trinity_git) before running the clone command. Took a couple of hours. Thereafter I never again used git clone, instead using switch_all_submodules_to_head_and_clean, like this: cd /home/public/builds/slackware/trinity/zz_src_trinity_git sh ./scripts/switch_all_submodules_to_head_and_clean anonymous After a few times I automated the latter process into a script with a few bells and whistles. I wonder whether manually deleting all of the "config" files would clean the local repository: find $GIT_DIR -type f -name config -exec rm -f {} \; Then perform a clone: cd $GIT_DIR_ROOT git clone http://scm.trinitydesktop.org/scm/git/tde $GIT_DIR I'm using GIT 1.7.1. Now that I am using a password I wonder whether I can connect anonymously. I'll try that the next day or two when I rsync my local tree. Darrell

On 02/29/2012 08:02 PM, Keith Daniels wrote: Thank you Keith, I have gotten away from using the stock scripts entirely due to this problem. I have my local git tree in $HOME/tde/tde. So I created a separate script directory that holds my modified scripts to update the git tree in $HOME/tde/scr. Now when I need to update the tree, I do the following: cd $HOME/tde/tde ../scr/switch_dcr.sh The switch_dcr.sh is just my version of switch_all_submodules_to_head_and_clean that has the --recursive flags added: 10:55 providence:~/tde/tde> cat ../scr/switch_dcr.sh #!/bin/bash git reset --hard HEAD git clean -dxf git pull git reset --hard HEAD git clean -dxf sed -i "s/system@/drankin@/g" .gitmodules git submodule init git submodule update --recursive git submodule foreach --recursive "git checkout master" git submodule foreach --recursive "git pull" git checkout -- .gitmodules exit 0 The sed line (in the original script as well) fixed the system@ issue for me. Since I have used this method for updating the tree, I have had no more issues. However, I did have many problems with the original download of the tree not filling the admin and cmake directories with the submodules. I ran several tests. The one that seemed to work the best was do loop through each dir in main and call the switch_dcr.sh script. For example: cd $HOME/tde/tde/main for i in *; do cd $HOME/tde/tde/main/${i}; $HOME/tde/scr/switch_dcr.sh; done Then I would cd into dependencies and applications and run the same for loop and step through the individual packages calling switch_dcr.sh as above. After I did that, then for every update after that, all I needed to do was to call the switch_dcr.sh update script from the top of the tree ($HOME/tde/tde) and it would now correctly pull in submodules for everything. I still don't know exactly where the original problem was, but some (or all) of the problem was related to the new version that Arch has. (version 1.7.9.2-1) Let us know what you find. -- David C. Rankin, J.D.,P.E.

First do this from the command line: export GIT_TREE_ROOT="/home/keith/builds/slackware/trinity" export GIT_TREE="zz_src_trinity_git" mkdir -p $GIT_TREE_ROOT/$GIT_TREE cd $GIT_TREE_ROOT git clone --recursive http://scm.trinitydesktop.org/scm/git/tde $GIT_TREE Then modify your script like this: GIT_TREE_ROOT="/home/keith/builds/slackware/trinity" GIT_TREE="zz_src_trinity_git" if [ -d $GIT_TREE_ROOT/$GIT_TREE ]; then cd $GIT_TREE_ROOT/$GIT_TREE sh ./scripts/switch_all_submodules_to_head_and_clean anonymous else mkdir -p $GIT_TREE_ROOT/$GIT_TREE cd $GIT_TREE_ROOT git clone --recursive http://scm.trinitydesktop.org/scm/git/tde $GIT_TREE fi Darrell

The web interface is not exactly the same as the full directory structure: http://git.trinitydesktop.org/cgit/tde/tree/scripts Darrell