From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: insight-announce@sourceware.cygnus.com Subject: [Fwd: New GDB CVS repository is set up!] Date: Wed, 09 Feb 2000 01:54:00 -0000 Message-id: <38A12FDB.5715CF81@cygnus.com> X-SW-Source: 2000/msg00000.html FYI. The CVS module ``insight'' will check out all of the insight components. Sorry to not forward this on earlier. (unless Jason already has) Andrew To : gdb at sourceware dot cygnus dot com, gdb-testers at sourceware dot cygnus dot com Subject : New GDB CVS repository is set up! >From : Jason Molenda Date : Sun, 6 Feb 2000 22:43:15 -0800 Hi folks! The new GDB repository is set up. If you have a checked out copy of the GDB repository, you're going to check out a brand new one. Read this whole message. This weekend I merged the GDB repository with the binutils repository which was already on Sourceware. For those of you working on both gdb and binutils, the merging of these two will ease your life considerably. I treated the binutils repository as the master repository, so whenever there was overlap between the gdb repository and the binutils repository, the files from the binutils repository were used. Binutils and GDB have not been synchronized/merged in approx six months, so we're going to have some instability this week. Cygwin support in binutils is just plain broken right now. :-/ The following directories from the GDB repository were incorporated in to the new repository with no changes: dejagnu, expect, gdb, mmalloc, readline, sim, tcl, utils The following directories from the binutils repository were incorporated in to the new repository with no changes: bfd, config, etc, gas, gprof, include, intl, ld, libiberty, opcodes, texinfo And all of the top-level files were from binutils as well. If you have changes in your checked-out tree, and the changes are all in the directories that came from GDB, you are fine -- do a cvs diff of your existing tree, check out a new tree and apply the patches. They'll apply cleanly. If you have changes in your checked-out tree in the directories from the binutils repository, you should still do the diff in the old GDB repository so you have a clear idea of what you changed, but the changes may not apply cleanly to the binutils version of that directory. You may need to do some work to get it applied cleanly. Most people will have few, or no, changes to their checked out copy of the GDB repository. Those people should just remove their checked out copy and get a new one. Andrew Cagney suggested that a lot of people will do this, so I've tarred up pre-checked-out trees using the anoncvs pserver method -- just download one of these tarfiles and you'll be good to go. In ftp://sourceware.cygnus.com/pub/gdb/snapshots/ you'll find: 9102999 Feb 6 19:38 gdb-pserver-2000-02-06.tar.bz2 2230176 Feb 6 19:42 dejagnu-pserver-2000-02-06.tar.bz2 11027699 Feb 6 20:01 gdb-dejagnu-pserver-2000-02-06.tar.bz2 14246962 Feb 6 20:20 insight-pserver-2000-02-06.tar.bz2 The "gdb-pserver-2000-02-06.tar.bz2" is just GDB. The "dejagnu-pserver-2000-02-06.tar.bz2" is just dejagnu. The "gdb-dejagnu-pserver-2000-02-06.tar.bz2" is GDB and dejagnu. The "insight-pserver-2000-02-06.tar.bz2" is Insight. If you want to check out a tree for yourself, the instructions on the GDB web page ( http://sourceware.cygnus.com/gdb/ ) are updated. In short, you want to do cvs -z9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src login ("anoncvs" for the password) cvs -z9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src co gdb As I wrote previously, changes to the GDB repository will now happen almost entirely in this public repository. If you want to see cvs commit messages as they happen, sign up to the gdb-cvs mailing list (there are instructions on the GDB home page for getting on this) or monitor its web archive. Much credit for this repository move goes to Andrew Cagney who has been moving (literally) mountains of code in the face of lame Australian infrastructure :-) and an already heavy work load. This move would have been a disaster without the overdue reorganizations and cleanups he did last week. Thanks Andrew! This is a significant change, and I expect some people to have problems. I doubt I've thought of every possible confusion or complication in this move. Ask me if you have any questions. Jason Free the Software!