cvs commit: apache-devsite devnotes.html
fanf99/12/14 09:46:15 Modified:.devnotes.html Log: the agent may have more than one key Revision ChangesPath 1.14 +1 -1 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- devnotes.html 1999/12/14 17:45:17 1.13 +++ devnotes.html 1999/12/14 17:46:15 1.14 @@ -225,7 +225,7 @@ without having to enter a password for each CVS operation. Use ssh-add and enter your passphrase once when you start a session, and ssh-add -D at the end of the session to -delete your unencrypted key from the agent. +delete your unencrypted key(s) from the agent.
cvs commit: apache-devsite devnotes.html
fanf99/12/14 09:45:17 Modified:.devnotes.html Log: One of my colleages noted that this page recommends using unencrypted ssh keys. It's better to use the ssh-agent. Submitted by: Mike Bristow <[EMAIL PROTECTED]> Revision ChangesPath 1.13 +6 -5 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- devnotes.html 1999/10/12 21:47:08 1.12 +++ devnotes.html 1999/12/14 17:45:17 1.13 @@ -220,11 +220,12 @@ On your local system generate your SSH public key file ~/.ssh/identity.pub via ssh-keygen and then put -it in ~/.ssh/authorized_keys on the repository system. This -will allow you to access the repository without having to enter a password -for each CVS operation. But make sure that you didn't enter a passphrase -when running ssh-keygen or you need to enter that one -instead of the password (which would be no gain). +it in ~/.ssh/authorized_keys on the repository system. If you +use the ssh-agent this will allow you to access the repository +without having to enter a password for each CVS operation. Use +ssh-add and enter your passphrase once when you start a +session, and ssh-add -D at the end of the session to +delete your unencrypted key from the agent.
cvs commit: apache-devsite devnotes.html
brian 99/10/12 14:47:09 Modified:.devnotes.html Log: When used with the slash, it can cause problems with Karma (looking for /apache-devsite instead of apache-devsite in avail, for example). Revision ChangesPath 1.12 +1 -1 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- devnotes.html 1999/01/05 15:51:12 1.11 +++ devnotes.html 1999/10/12 21:47:08 1.12 @@ -205,7 +205,7 @@ repository system: - setenv CVSROOT /home/cvs/ + setenv CVSROOT /home/cvs setenv CVS_RSH /usr/local/bin/ssh
cvs commit: apache-devsite devnotes.html
stoddard99/01/05 07:51:12 Modified:.devnotes.html Log: Update broken link to SSH site. Revision ChangesPath 1.11 +1 -1 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- devnotes.html 1998/12/04 22:12:03 1.10 +++ devnotes.html 1999/01/05 15:51:12 1.11 @@ -173,7 +173,7 @@ page for information about how the group works and people get access to the CVS repository.) One way to set this up using the http://www.cs.hut.fi/ssh/"; + HREF="http://www.ssh.fi/sshprotocols2/index.html"; >ssh (secure shell) tool:
cvs commit: apache-devsite devnotes.html
brian 98/12/04 14:12:04 Modified:.devnotes.html Log: The complete repository has not been available for download in a snapshot in quite some time. Revision ChangesPath 1.10 +0 -42 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- devnotes.html 1998/11/24 17:15:52 1.9 +++ devnotes.html 1998/12/04 22:12:03 1.10 @@ -161,48 +161,6 @@ - Using the CVS Repository Copy - - - For those who wish to keep up with the source development but are not - members of the Group or have access to the master CVS repository, a - snapshot tarball of the repository is created daily. You can - copy this to your system, unpack it, and treat it as a read-only - repository. - - - Pick up the latest tarball of the repository from - - - ftp://ftp.apache.org/httpd/from-cvs/repository.tar.gz"; - >ftp://ftp.apache.org/httpd/from-cvs/repository.tar.gz - - - - -Note that this is the complete repository, not just the -latest development stream. - - - On your local system, unpack the tarball into a directory: - - - % cd /usr/local/apache/repository - - % gunzip -c < repository.tar.gz | tar xf - - - - - - - - You can now use cvs checkout and cvs update - to create and update your own working directories from the latest CVS - snapshot. - - - Setting Up Remote CVS
cvs commit: apache-devsite devnotes.html
brian 98/04/19 22:36:29 Modified:.devnotes.html Log: Remind folks about the .indent.pro files. Revision ChangesPath 1.8 +4 -2 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- devnotes.html 1998/02/11 13:04:31 1.7 +++ devnotes.html 1998/04/20 05:36:29 1.8 @@ -68,8 +68,10 @@ -(The /tmp/foo file is mailed to the developers list so -they can consider the value/validity of the patch.) +The /tmp/foo file is mailed to the developers list so +they can consider the value/validity of the patch. It is also worth +making sure your code follows the Apache style, as described by the +GNU indent flags in the .indent.pro file in every source directory. Once other developers have agreed that the change is a Good
cvs commit: apache-devsite devnotes.html
rse 98/02/11 05:04:31 Modified:.devnotes.html Log: URL has moved some time ago and this link was missing. Revision ChangesPath 1.7 +2 -2 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- devnotes.html 1998/01/30 09:32:08 1.6 +++ devnotes.html 1998/02/11 13:04:31 1.7 @@ -274,8 +274,8 @@ Ralf Engelschall has written an excellent explanation on how to use remote CVS with the "cvsup" functionality we have available now. -http://www.engelschall.com/pw/private/apacherepos/";> -http://www.engelschall.com/pw/private/apacherepos/ +http://www.engelschall.com/pw/apache/cvsguide/";> +http://www.engelschall.com/pw/apache/cvsguide/
cvs commit: apache-devsite devnotes.html
dgaudet 98/01/30 01:32:09 Modified:.devnotes.html Log: update Revision ChangesPath 1.6 +20 -6 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- devnotes.html 1998/01/09 16:26:02 1.5 +++ devnotes.html 1998/01/30 09:32:08 1.6 @@ -90,12 +90,9 @@ There are several different modules in the Apache CVS repository: - apache + apache-1.2 - At the time this document is being written, this is the main -development stream for Apache 1.3. It also contains branches for -the 1.1 and 1.2 versions, though. - + To create a directory tree containing the 1.2.x sources, and call it apache-1.2, change your current directory to the parent of the tree and then check the 1.2 sources @@ -105,7 +102,24 @@ % cd /usr/local/apache - % cvs checkout -rAPACHE_1_2_X -d apache-1.2 apache + % cvs checkout apache-1.2 + + + + + apache-1.3 + + +To create a directory tree containing the 1.3 sources, +and call it apache-1.3, change your current directory +to the parent of the tree and then check the 1.3 sources +out as follows: + + + + % cd /usr/local/apache + + % cvs checkout apache-1.3
cvs commit: apache-devsite devnotes.html voting.html
coar98/01/09 08:26:05 Modified:.devnotes.html voting.html Log: Change the notes about context diffs to refer to unified diffs instead, since that's the current operating norm. Submitted by: Martin Kraemer Revision ChangesPath 1.5 +1 -1 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- devnotes.html 1997/12/02 00:26:44 1.4 +++ devnotes.html 1998/01/09 16:26:02 1.5 @@ -63,7 +63,7 @@ them: - % cvs diff -c3 apache/src/mod_mime.c > /tmp/foo + % cvs diff -u apache/src/mod_mime.c > /tmp/foo 1.4 +2 -2 apache-devsite/voting.html Index: voting.html === RCS file: /export/home/cvs/apache-devsite/voting.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- voting.html 1997/08/26 14:02:36 1.3 +++ voting.html 1998/01/09 16:26:02 1.4 @@ -203,10 +203,10 @@ Patch Format -The patch should be created by using diff -C3 on the +The patch should be created by using diff -u on the CURRENT source and the modified source. E.g., -diff -C3 http_main.c.orig http_main.c +diff -u http_main.c.orig http_main.c All patches necessary to address an action item must be concatenated within a single patchfile. The source files affected by the patchfile
cvs commit: apache-devsite devnotes.html
brian 97/12/01 16:26:46 Modified:.devnotes.html Log: Revision ChangesPath 1.4 +12 -0 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- devnotes.html 1997/07/31 15:52:27 1.3 +++ devnotes.html 1997/12/02 00:26:44 1.4 @@ -253,6 +253,18 @@ instead of the password (which would be no gain). + + +Working with the Apache Source CVS Repository remotely + +Ralf Engelschall has written an excellent explanation on how to use +remote CVS with the "cvsup" functionality we have available now. + +http://www.engelschall.com/pw/private/apacherepos/";> +http://www.engelschall.com/pw/private/apacherepos/ + + +
cvs commit: apache-devsite devnotes.html
rse 97/07/31 08:52:28 Modified:. devnotes.html Log: fixed typo and added more details on how to access the repository over SSH. Revision ChangesPath 1.3 +8 -5 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- devnotes.html 1997/07/15 11:14:27 1.2 +++ devnotes.html 1997/07/31 15:52:27 1.3 @@ -223,7 +223,7 @@ -Adjust the lasat two paths to correctly reflect the locations of +Adjust the last two paths to correctly reflect the locations of cvs and ssh on your local system. @@ -244,10 +244,13 @@ so you don't need to edit them. - Generate and put your ssh public key file in -~/.ssh/authorized_keys on the repository system. This -will allow you to access the repository without having to enter a -passphrase for each CVS operation. + On your local system generate your SSH public key file +~/.ssh/identity.pub via ssh-keygen and then put +it in ~/.ssh/authorized_keys on the repository system. This +will allow you to access the repository without having to enter a password +for each CVS operation. But make sure that you didn't enter a passphrase +when running ssh-keygen or you need to enter that one +instead of the password (which would be no gain).
cvs commit: apache-devsite devnotes.html index.html
coar97/07/15 04:14:28 Modified:. devnotes.html index.html Log: Correct a cut/paste error Brian spotted, add stuff about using the CVS snapshot, and link into the dev.apache.org front door. Revision ChangesPath 1.2 +43 -1 apache-devsite/devnotes.html Index: devnotes.html === RCS file: /export/home/cvs/apache-devsite/devnotes.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C3 -r1.1 -r1.2 *** devnotes.html 1997/07/13 20:43:33 1.1 --- devnotes.html 1997/07/15 11:14:27 1.2 *** *** 145,150 --- 145,192 +Using the CVS Repository Copy + + + For those who wish to keep up with the source development but are not + members of the Group or have access to the master CVS repository, a + snapshot tarball of the repository is created daily. You can + copy this to your system, unpack it, and treat it as a read-only + repository. + + +Pick up the latest tarball of the repository from + + + ftp://ftp.apache.org/httpd/from-cvs/repository.tar.gz"; + >ftp://ftp.apache.org/httpd/from-cvs/repository.tar.gz + + + + + Note that this is the complete repository, not just the + latest development stream. + + +On your local system, unpack the tarball into a directory: + + + % cd /usr/local/apache/repository + + % gunzip -c < repository.tar.gz | tar xf - + + + + + + + You can now use cvs checkout and cvs update + to create and update your own working directories from the latest CVS + snapshot. + + + Setting Up Remote CVS *** *** 174,180 setenv CVSROOT repository-system:/export/home/cvs ! setenv CVS_RSH /usr/local/bin/cvs setenv CVS_SERVER /usr/local/bin/cvs --- 216,222 setenv CVSROOT repository-system:/export/home/cvs ! setenv CVS_RSH /usr/local/bin/ssh setenv CVS_SERVER /usr/local/bin/cvs 1.5 +5 -0 apache-devsite/index.html Index: index.html === RCS file: /export/home/cvs/apache-devsite/index.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C3 -r1.4 -r1.5 *** index.html1997/07/02 03:07:29 1.4 --- index.html1997/07/15 11:14:27 1.5 *** *** 74,79 --- 74,84 >module magic number (last modified on ) +Random notes about + using CVS and maintaining the Apache site + The
cvs commit: apache-devsite devnotes.html
coar97/07/13 13:43:33 Added: . devnotes.html Log: Rough draft/outline/collection of notes about the nitty-gritty details of working on Apache. Revision ChangesPath 1.1 apache-devsite/devnotes.html Index: devnotes.html === Apache Development Notes Apache Development Notes This page is intended to provide some basic background about development nits and the maintenance of the developer site. Maintaining the Sources Almost all files relating to Apache, either the actual sources or the files that aren't part of the distribution, are maintained in a ftp://ftp.eece.maine.edu/archive/pub/src/alpha/gnu/cvs-1.9.tar.gz"; >CVS repository. Here is the way in which changes are applied: Developer checks out a copy of the files on which it wants to work, into a private working directory: % cvs checkout apache This step only needs to be performed once. Developer keeps its working directory synchronised with changes made to the repository: % cvs update apache This should probably be done daily or even more frequently during periods of high activity. Developer makes changes to its working copies, makes sure they work, and generates a patch so others can apply the changes to test them: % cvs diff -c3 apache/src/mod_mime.c > /tmp/foo (The /tmp/foo file is mailed to the developers list so they can consider the value/validity of the patch.) Once other developers have agreed that the change is a Good Thing, the developer checks the changes into the repository: % cvs commit apache/src/mod_mime.c CVS Modules There are several different modules in the Apache CVS repository: apache At the time this document is being written, this is the main development stream for Apache 1.3. It also contains branches for the 1.1 and 1.2 versions, though. To create a directory tree containing the 1.2.x sources, and call it apache-1.2, change your current directory to the parent of the tree and then check the 1.2 sources out as follows: % cd /usr/local/apache % cvs checkout -rAPACHE_1_2_X -d apache-1.2 apache apache-site This module contains the files that live at http://www.apache.org/. The directory on the host that maps to that URL is actually a set of checked-out working copies of the CVS files. Note It is important that the files on the Web host not be modified directly. If you want or need to change one, check it out into a private working copy, modify that, commit the change into CVS, and then perform a cvs update to bring the host directory into sync with the CVS sources. The Web site directories are not maintained in synch with the CVS files automatically. They are manually updated from CVS by various people as they consider appropriate. This is usually not an issue, unless a group of files are being updated according to an ongoing group discussion. apache-devsite Like the apache-site module, this one is used ot maintain the files that comprise a Webs site - in this case, http://dev.apache.org/. Also like the previous module, the directory on the server is a checked-out working copy of this module. Setting Up Remote CVS Most of the Apache Group members with access to the CVS repository actually do their work on their local machines and keep synchronised with the repository through remote CVS. See the http://www.apache.org/ABOUT_APACHE.html"; >ABOUT APACHE page for information about how the group works and people get access to the CVS repository.) One way to set this up using the http://www.cs.hut.fi/ssh/"; >ssh (secure shell) tool: You need an account on the Apache repository system. If you've been "voted in" for direct access to the repository, this should have been set up for you. Include the following in your login files on your local (UNIX) machine: setenv CVSROOT repository-system:/export/home/cvs setenv CVS_RSH /usr/local/bin/cvs setenv CVS_SERVER /usr/local/bin/cvs Ad
