[22713] branches/release_1_4/Makefile.in

[source_changes at macosforge.org]

Revision: 22713
          http://trac.macosforge.org/projects/macports/changeset/22713
Author:   jmpp at macports.org
Date:     2007-03-12 11:54:09 -0700 (Mon, 12 Mar 2007)

Log Message:
-----------

Out with README_RELEASE1 and in with our new Wiki!

As a side note, I believe the main Makefile should at least run checks for the 'all' target
when 'install' is called, so that "make install" works all the way if a plain "make" hasn't
been called before; currently, what happens is that make fails on the src/port dir
(and probably elsewhere) if the 'all' target is not called explicitly. Could someone more
acquainted than me with our Makefiles take a look at this? (hint: Landon? ;) All these
includes and double colon rules confuse me!

Modified Paths:
--------------
    branches/release_1_4/Makefile.in

Modified: branches/release_1_4/Makefile.in
===================================================================
--- branches/release_1_4/Makefile.in	2007-03-12 18:46:58 UTC (rev 22712)
+++ branches/release_1_4/Makefile.in	2007-03-12 18:54:09 UTC (rev 22713)
@@ -41,13 +41,11 @@
 	fi
 
 	@echo ""
-	@echo "Congratulations, you have successfully installed the MacPorts system."
+	@echo "Congratulations, you have successfully installed the MacPorts system. To get the Portfiles and update the system run:"
 	@echo ""
-	@echo "To get the Portfiles and update the system run:"
-	@echo ""
 	@echo "sudo port selfupdate"
 	@echo ""
-	@echo "Please read README_RELEASE1 and port(1)."
+	@echo "Please read port(1) and the MacPorts Wiki at http://trac.macports.org/ for full documentation."
 	@echo ""
 
 clean::

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070312/e3ac097f/attachment.html