[svn:parrot] r43561 - trunk

barney at svn.parrot.org barney at svn.parrot.org
Sat Jan 23 11:38:30 UTC 2010


Author: barney
Date: Sat Jan 23 11:38:29 2010
New Revision: 43561
URL: https://trac.parrot.org/parrot/changeset/43561

Log:
Removed reference to 'make install-dev' in README.
Point to parrot-users as the entry level mailing list.
Removed POD markup.

Modified:
   trunk/README

Modified: trunk/README
==============================================================================
--- trunk/README	Sat Jan 23 11:33:17 2010	(r43560)
+++ trunk/README	Sat Jan 23 11:38:29 2010	(r43561)
@@ -23,7 +23,7 @@
 for running various configure and build scripts.
 
 For most of the platforms that we are supporting initially, Parrot should build
-out of the box. docs/parrot.pod lists the core platforms.  PLATFORMS provides
+out of the box. docs/parrot.pod lists the core platforms. PLATFORMS provides
 reports on the platforms on which Parrot has been built and tested.
 
 INSTRUCTIONS
@@ -85,13 +85,6 @@
 But please note that dynamic libs will not be found for non-standard
 locations unless you set LD_LIBRARY_PATH or similar.
 
-If you want to build high level languages on top of Parrot, you should
-also run
-
-    make install-dev
-
-to install development files which compilers need in their build process.
-
 Look at docs/parrot.pod and docs/intro.pod for where to go from here.  If you
 have any problems, see the section "How To Submit A Bug Report" in
 docs/submissions.pod.  These documents are in POD format. You can view these
@@ -116,14 +109,16 @@
 MAILING LISTS
 -------------
 
-The mailing list for Parrot is parrot-dev at lists.parrot.org. Subscribe by
-filling out the form at http://lists.parrot.org/mailman/listinfo/parrot-dev
-It is archived at http://lists.parrot.org/pipermail/parrot-dev/
+The Parrot user mailing list is parrot-users at lists.parrot.org. Subscribe by
+filling out the form at http://lists.parrot.org/mailman/listinfo/parrot-users .
+The list is archived at http://lists.parrot.org/pipermail/parrot-users/ .
+
+For development discussions see the information in docs/gettingstarted.pod.
 
 FEEDBACK, PATCHES, etc.
 -----------------------
 
-See F<docs/submissions.pod> for more information on reporting bugs and
+See docs/submissions.pod for more information on reporting bugs and
 submitting patches.
 
 WEB SITES


More information about the parrot-commits mailing list