The main topics explained here are the development process and the
internals.
-Even though this document describes how to build the source code from
-the CVS, you should notice that it is intentional that we don't put
-the instruction on the Web page--that is, pointless complaints about
-development versions are _unwelcome_ to us.
-
-If you are a beginning user, who just wants to try the "newer" product
-from the CVS, abandon the bad idea and stick on the released version.
-
* Development process
** Reporting bugs
-You can create a template of a bug report by `M-x
-riece-submit-bug-report'. This command assumes that riece-debug is t.
-
-If riece-debug is t, "*Debug*" buffer will have debugging information.
-Also, interactions with IRC servers will be written to "
-*IRC*<IRC-server-name>" buffers. Note that these buffers have a name
-starting with a whitespace character (" ").
+If you find a bug, please file it at
+https://savannah.nongnu.org/bugs/?group=riece
** Contributing code
** Getting the development source code
-Again, use the released version if you are a beginning user and not
-willing to become a developer.
+The development of Riece uses Git. The latest development version is
+available from git.sv.gnu.org.
-The development of Riece uses CVS. The latest development version is
-available from cvs.m17n.org. The instructions to obtain and build the
-source from the CVS are below.
+NOTE: If you are a beginning user, who just wants to try the "newer"
+version, stick on the latest released version. Pointless complaints
+about development versions are unwelcome to us.
-(1) checkout modules
+The instructions to obtain and build the source from Git are below.
- cvs -d :pserver:anonymous@cvs.m17n.org:/cvs/root checkout riece
+(1) checkout modules
-You can specify a tag in front of the module name.
+ git clone git://git.sv.gnu.org/riece.git
(2) generate configure script
projects / riece / blobdiff