Return-Path: Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Delivered-To: mailing list dev@apr.apache.org Received: (qmail 71718 invoked from network); 16 Nov 2000 21:17:14 -0000 Received: from sfo-gw.covalent.net (HELO koj.covalent.net) (207.44.198.62) by locus.apache.org with SMTP; 16 Nov 2000 21:17:14 -0000 Received: from rbb (helo=localhost) by koj.covalent.net with local-esmtp (Exim 3.16 #1) id 13wWQf-00052O-00; Thu, 16 Nov 2000 13:18:45 -0800 Date: Thu, 16 Nov 2000 13:18:45 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj.rkbloom.net To: dev@apr.apache.org cc: new-httpd@apache.org Subject: Splitting APR from Apache. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is scheduled to happen early next week, and we still need to decide how to go about doing this. Here is my thought on the matter. 1) On locus: cp -R /home/cvs/apache-2.0/src/lib/apr /home/cvs/apr 2) On remote machine cd apache-2.0/src/lib/ cvs rm -R apr cvs commit apr cd cvs co apr cp -R apr apache-2.0/src/lib cvs import apr This allows us to keep the history for APR with the actual code, which is where it belongs. This also allows us keep APR with Apache, which should take care of some of the harrier issues that came up when splitting the docs tree. The final part to this, is that we would need to do a fresh cvs import as a cron job on locus every once in a while. I would suggest starting with once a week, and moving it up as necessary. I would expect any developer working on both APR and Apache to do: cvs co apache-2.0 cd apache-2.0/src/lib rm -Rf apr cvs co apr I'm not 100% sure this will work, but it sounds and looks like it will to me. Thoughts? Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------