swift 05/06/01 20:40:09 Modified: xml/htdocs/doc/en macos-guide.xml Log: Small updates thanks to r2d2
Revision Changes Path 1.6 +9 -8 xml/htdocs/doc/en/macos-guide.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo Index: macos-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- macos-guide.xml 21 Dec 2004 08:01:22 -0000 1.5 +++ macos-guide.xml 1 Jun 2005 20:40:09 -0000 1.6 @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v 1.5 2004/12/21 08:01:22 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v 1.6 2005/06/01 20:40:09 swift Exp $ --> <guide link="/doc/en/macos-guide.xml"> @@ -32,8 +32,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> <license/> -<version>1.3</version> -<date>2004-11-25</date> +<version>1.4</version> +<date>2005-06-01</date> <chapter> <title>Installation</title> @@ -162,7 +162,7 @@ </pre> <pre caption="Aliasing your default profile for Tiger"> -# <i>ln -s /usr/portage/profiles/default-darwin/macos/10.3 /etc/make.profile</i> +# <i>ln -s /usr/portage/profiles/default-darwin/macos/10.4 /etc/make.profile</i> </pre> <note> @@ -221,7 +221,7 @@ <p> You should be able to emerge any combination of packages that have already been tested and updated to work with macos. Currently, only a very small number of -packages are not masked. If an ebuild hasn't had the macos keyword added to it, +packages are not masked. If an ebuild hasn't had the ppc-macos keyword added to it, you will get a message similar to the following. </p> @@ -246,8 +246,8 @@ You might want to test a package yourself to see if it works, regardless of it's masked state. While we do not suggest that the average user do this, people that wish to help the developers in testing packages are free to unmask and test -packages on their system. This is done by adding the 'macos' keyword to an -package information file, or 'ebuild'. To add the macos keyword to an ebuild, +packages on their system. This is done by adding the 'ppc-macos' keyword to an +package information file, or 'ebuild'. To add the ppc-macos keyword to an ebuild, you use the 'ekeyword' command, which is part of the the gentoolkit-dev package. </p> @@ -258,6 +258,7 @@ <pre caption="Keywording a package"> # <i>cd /usr/portage/games-misc/cowsay</i> # <i>ekeyword ppc-macos cowsay-3.03.ebuild</i> +# <i>ebuild cowsay-3.03.ebuild digest</i> </pre> <p> @@ -482,7 +483,7 @@ <p> According to Gentoo for Mac OS X policy, ebuilds that install libraries must be -checked to be in working order before they are keyworded as 'macos'. Most of the +checked to be in working order before they are keyworded as 'ppc-macos'. Most of the time, the reason that the libraries are nonworking is that the libary simply references incorrect paths. For the adventurers out there, there's a simple workaround for this. The <c>ranlib</c> command fixes, amongst other things, -- [email protected] mailing list
