From 9a06b47595ad067bb6aad251a6ce47068b6a8fd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mikael=20Brandstr=C3=B6m?= <mikael@brandstrom.org>
Date: Mon, 8 Apr 2002 19:02:43 +0200
Subject: [PATCH] * Added instructions for getting pike from cvs. * Added
README-CVS.txt to the dists.
Rev: README-CVS.txt:1.14
Rev: bin/export.pike:1.45
---
README-CVS.txt | 37 ++++++++++++++++++++++++++++++++-----
bin/export.pike | 4 ++--
2 files changed, 34 insertions(+), 7 deletions(-)
diff --git a/README-CVS.txt b/README-CVS.txt
index 7c21c3c817..e5ec15d766 100644
--- a/README-CVS.txt
+++ b/README-CVS.txt
@@ -1,15 +1,42 @@
-$Id: README-CVS.txt,v 1.13 2002/04/06 20:49:08 mikael%unix.pp.se Exp $
+$Id: README-CVS.txt,v 1.14 2002/04/08 17:02:43 mikael%unix.pp.se Exp $
HOW TO BUILD PIKE FROM CVS
-The top-level makefile (in this directory, not the src directory) has
-all the magic you need to build pike directly from CVS. Just type
-'make'.
+If you like to live at the bleeding edge you can download pike from CVS
+whith all the latest additions from the developers. There are two
+major branches in the archive, the latest stable branch and latest
+development branch. Stable versions have an even minor version number,
+ie. 7.0.x, 7.2.x, 7.4.x wheras the development branches have an odd
+minor version.
+
+Keep in mind that the cvs versions are under heavy development and
+have not been tested nearly as well as the offcial releases. You use
+the code at YOUR OWN RISK.
+
+There are a few simple steps to get pike from cvs:
+1. Get a recent version of cvs.
+2. Login to the cvs-server:
+
+ cvs -d :pserver:anon@cvs.roxen.com:/cvs login
+
+ just hit enter on the password prompt
+3. Check out the source:
-Building Pike from cvs, in addition to the requirements for a normal
+ cvs -z3 -d :pserver:anon@cvs.roxen.com:/cvs co Pike/7.3
+
+ subistute 7.3 for whatever version you want to get.
+
+Building Pike from cvs, in addition to the requirements of a normal
build, requires a working Pike. You will also need automake, gnu m4
and bison.
+The top-level makefile (in this directory, not the src directory) has
+all the magic you need to build pike directly from CVS. Just type
+'make'. It is preferable to build from the toplevel since it avoids
+contaminating the source tree with object files and other generated
+files.
+
+
Other interesting make targets are:
install compile and install in default location
diff --git a/bin/export.pike b/bin/export.pike
index a7e6ad91cd..805d2e6446 100755
--- a/bin/export.pike
+++ b/bin/export.pike
@@ -1,6 +1,6 @@
#! /usr/bin/env pike
-/* $Id: export.pike,v 1.44 2002/04/07 15:19:02 nilsson Exp $ */
+/* $Id: export.pike,v 1.45 2002/04/08 17:02:43 mikael%unix.pp.se Exp $ */
multiset except_modules = (<>);
string vpath;
@@ -196,7 +196,7 @@ int main(int argc, array(string) argv)
files=`+( ({ vpath+"/README.txt", vpath+"/ANNOUNCE",
vpath+"/COPYING", vpath+"/COPYRIGHT",
- vpath+"/Makefile" }),
+ vpath+"/Makefile", vpath+"/README-CVS.txt" }),
get_files(vpath+"/src"),
get_files(vpath+"/lib"),
get_files(vpath+"/bin"),
--
GitLab