Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jimmy Guo <guo@cup.hp.com>
To: gdb@sourceware.cygnus.com
Subject: Re: cvsup & sourceware repositories?
Date: Thu, 16 Mar 2000 22:45:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10003162342590.8409-100000@hpcll168.cup.hp.com> (raw)

<< added the missing command line I mentioned at the end of the message >>

OK, here is a summary of the steps involved for me to create a local
repository behind a firewall:

- SOCKS5 (needed if you are behind a firewall)
  + Download:
    http://www.socks.nec.com/cgi-bin/download.pl

  + Build and install.

  + Configure to use a socks5 server your site provides:
    * Create /etc/libsocks5.conf:
sockd @=<your_socks_server>,<your_socks_server>.<domain> 0.0.0.0 0.0.0.0

  + Reference:
    http://www.socks.nec.com/socksv5.html

  + How to socksify an application:
    http://www.socks.nec.com/how2socksify.html

- CVS
  + Download:
    http://www.cyclic.com/pub/

  + Build and install.

  + Reference Manual, etc.:
    http://www.loria.fr/~molli/cvs-index.html

- rsync

  + Download:
    http://rsync.samba.org/

  + Socksify rsync source (needed if you are going to use rsync from
    behind a firewall), the quick'n'dirty approach:
    * main.c (main): add 'SOCKSinit (argv[0]);' to the beginning
    of main ().
    + rsync.h: add '#define SOCKS' and '#include <socks.h>' to the
    beginning of file.
    + Makefile.in: add '-L/usr/local/lib' (or the libsocks5 install
    location) and '-lsocks5' to the rsync link line.

  + Configure / Make / Install.

  + Reference:
    rsync(1) man page.
    http://sourceware.cygnus.com/sourceware/ under 'anonymous rsync' link.    

- Local repository creation:
  % mkdir -p <local_repository_root>
  % cd <local_repository_root>
  % rsync --archive --delete --checksum --compress --stats \
    rsync://sourceware.cygnus.com/src-cvs .

- Extract source (this creates <work_directory>/src/ tree with all
  necessary gdb and dejagnu components):
  % setenv CVSROOT <local_repository_root>
  % cd <work_directory>
  % cvs checkout -r HEAD dejagnu gdb

- Routine synchronization of src-cvs repository:
  Use the same rsync command above to synchronize.

That's it!  BTW the <local_repository_root>/CVSROOT/modules file lists
the module aliases / names in the repository, and I found it useful to
decide the module names to use in the cvs checkout command line.
Also, the rsync command line below dumps the list of repositories
available, which I used to figure out that the repository name
for src/cvs is actually src-cvs (that was not apparent to me as a
non-CVS user and was not mentioned in the
sourceware.cygnus.com/sourceware 'anonymous rsync' link):

  % rsync --archive --delete --checksum --compress --stats \
    rsync://sourceware.cygnus.com/ .

- Jimmy Guo, guo@cup.hp.com


>When you get it working, I would appreciate hearing about the procedure
>you used to (finally) make it work.  (You might just want to send a
>followup reply to gdb@sourceware because I suspect that there are others
>out there who'd also like to know.)


             reply	other threads:[~2000-03-16 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-16 22:45 Jimmy Guo [this message]
     [not found] <Pine.LNX.4.10.10003161941510.6569-100000@hpcll168.cup.hp.com>
2000-03-16 19:03 ` Jimmy Guo
  -- strict thread matches above, loose matches on Subject: below --
2000-03-16 16:29 Jimmy Guo
2000-03-16 16:37 ` Jim Kingdon
2000-04-01  0:00   ` Russ Allbery
2000-04-01  0:00 ` Andrew Cagney
2000-04-01  0:00 ` Jimmy Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10003162342590.8409-100000@hpcll168.cup.hp.com \
    --to=guo@cup.hp.com \
    --cc=gdb@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox