Commit | Line | Data |
---|---|---|
a88b0ab2 JB |
1 | Anonymous CVS access to Guile ======================================== |
2 | ||
3 | We make the current Guile sources available via anonymous CVS. Please | |
4 | keep in mind that these sources are strictly experimental; they will | |
5 | usually not be well-tested, and may not even compile on some systems. | |
6 | They may contain interfaces which will change. They will usually not | |
7 | be of sufficient quality for use by people not comfortable hacking the | |
8 | innards of Guile. Caveat! | |
9 | ||
10 | However, we're providing them anyway for several reasons. We'd like | |
11 | to encourage people to get involved in developing Guile. People | |
12 | willing to use the bleeding edge of development can get earlier access | |
13 | to new, experimental features. Patches submitted relative to recent | |
14 | sources will be easier for us to evaluate and install, since the | |
15 | patch's original sources will be closer to what we're working with. | |
16 | And it allows us to start testing features earlier. | |
17 | ||
5469b4a1 JB |
18 | Since the CVS tree is arranged for the convenience of the developers, |
19 | it requires GCC and GNU Make, which together support automatic | |
20 | dependency management. | |
21 | ||
a88b0ab2 JB |
22 | To check out a CVS working directory: |
23 | ||
24 | 1) Install CVS version 1.9 or later on your system. | |
25 | 2) Log into the CVS server: | |
8afdfa8e | 26 | $ cvs -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/guile login |
324a8d98 JB |
27 | At the prompt for `CVS password:', type `anoncvs'. |
28 | Once you have logged in, your password is saved in ~/.cvspass, and you | |
29 | will not need to enter it again. | |
a88b0ab2 | 30 | 3) Check out a module: |
8afdfa8e | 31 | $ cvs -z 9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/guile checkout guile-core |
a88b0ab2 JB |
32 | This should create a new directory `guile-core' in your current |
33 | directory, and populate it with the current Guile sources. | |
34 | ||
487f379f JB |
35 | The modules available for checkout are: |
36 | guile-core --- The scheme interpreter itself. | |
37 | guile-doc --- Guile documentation-in-progress. | |
4ebf0b3e | 38 | guile-oops --- GOOPS Guile Object Oriented Programming System. |
487f379f JB |
39 | guile-tcltk --- An interface between Guile and Tcl/Tk. |
40 | guile-scsh --- An incomplete port of SCSH 0.4.4 to Guile. | |
41 | guile-rgx-ctax --- This has been discontinued; use Andrew Archibald's | |
42 | distribution instead: | |
43 | ftp://ftp.red-bean.com/pub/guile/contrib/misc/guile-lang-allover-0.1.tar.gz | |
44 | ||
a88b0ab2 JB |
45 | Once you have a working directory, you can bring it up to date easily |
46 | and efficiently: | |
47 | ||
48 | 1) Go to the top directory of the source tree. That is, your current | |
49 | directory should be the one containing `configure.in', `README', | |
50 | and so on. | |
51 | 2) Do the update: | |
52 | $ cvs update | |
53 | ||
54 | This will incorporate any changes the developers have made to Guile | |
55 | since your last update into your source tree. | |
56 | ||
57 | The EGCS Project is kindly lending us space, time, and bandwidth on | |
58 | their CVS server. Thanks, folks! | |
59 | ||
60 | ||
a588d62c JB |
61 | Change Notification ================================================== |
62 | ||
63 | If you would like to receive mail when people commit changes to the | |
64 | Guile CVS repository, you can subscribe to guile-cvs@egcs.cygnus.com | |
65 | by sending a message to guile-cvs-subscribe@egcs.cygnus.com. Even | |
66 | better, you can get daily digests of these commit messages by sending | |
67 | a message to guile-cvs-digest-subscribe@egcs.cygnus.com. | |
68 | ||
69 | If you want to subscribe an e-mail address other than the one that | |
70 | appears in your From: header, say foo@bar.com, send a mail note to | |
71 | guile-cvs-subscribe-foo=bar.com@egcs.cygnus.com. | |
72 | ||
73 | ||
a88b0ab2 JB |
74 | Questions ============================================================ |
75 | ||
76 | (I don't know if they'll be "frequently asked" or not yet!) | |
77 | ||
78 | - It takes forever to do an update; what can I do to speed it up? | |
79 | ||
80 | CVS tries to be smart about what it sends; it will transmit and | |
81 | install only those files that have changed, and will sometimes | |
82 | transmit and apply patches instead, to save transmission time. | |
83 | ||
84 | It is also possible to have CVS compress transmitted data, using zlib. | |
85 | Put the following line in your ~/.cvsrc file: | |
86 | ||
87 | cvs -z 9 | |
88 | ||
89 | See the CVS documentation for more details. | |
90 | ||
91 | ||
92 | - What happens if I've changed files in my working directory, and then | |
93 | I do an update? | |
94 | ||
95 | If you have made local changes to your sources, the `cvs update' | |
96 | command will not overwrite them; instead, CVS will try to merge its | |
97 | changes with your changes, as if you had applied a patch. Rejects are | |
98 | marked in the sources. | |
99 | ||
100 | - Why does the build process try to run autoconf, aclocal, or automake? | |
101 | ||
102 | It shouldn't; if it does, that's a bug, I think. Those are the | |
103 | tools we use to generate `configure', `aclocal.m4', and the | |
104 | `Makefile.in' files from their respective sources. Ideally, you | |
105 | shouldn't need to have them installed, if you don't want to change | |
106 | those sources. If you do, see the section in `README' called | |
107 | `Hacking It Yourself'. |