| 1 |
neysx 05/11/26 00:12:31 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en macos-guide.xml metadoc.xml |
| 4 |
Log: |
| 5 |
#113577 ppc macos team asked u toremove this macos.xml guide |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.9 +11 -494 xml/htdocs/doc/en/macos-guide.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml?rev=1.9&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml?rev=1.9&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/macos-guide.xml.diff?r1=1.8&r2=1.9&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: macos-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v |
| 17 |
retrieving revision 1.8 |
| 18 |
retrieving revision 1.9 |
| 19 |
diff -u -r1.8 -r1.9 |
| 20 |
--- macos-guide.xml 21 Jun 2005 01:25:32 -0000 1.8 |
| 21 |
+++ macos-guide.xml 26 Nov 2005 00:12:31 -0000 1.9 |
| 22 |
@@ -1,521 +1,38 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v 1.8 2005/06/21 01:25:32 smithj Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/macos-guide.xml,v 1.9 2005/11/26 00:12:31 neysx Exp $ --> |
| 28 |
|
| 29 |
-<guide link="/doc/en/macos-guide.xml"> |
| 30 |
+<guide link="/doc/en/macos-guide.xml" disclaimer="obsolete" redirect="/proj/en/gentoo-alt/macos/"> |
| 31 |
|
| 32 |
-<title>Gentoo For Mac OS X Installation and Usage Guide</title> |
| 33 |
+<title>Gentoo For Mac OS X</title> |
| 34 |
|
| 35 |
-<author title="Author, Editor"> |
| 36 |
- <mail link="alexander@g.o">Alexander Plank</mail> |
| 37 |
-</author> |
| 38 |
-<author title="Author, Editor"> |
| 39 |
- <mail link="gongloo@g.o">Hasan Khalil</mail> |
| 40 |
-</author> |
| 41 |
-<author title="Author"> |
| 42 |
- <mail link="pat2man@×××××××.net">Patrick Tescher</mail> |
| 43 |
-</author> |
| 44 |
<author title="Author"> |
| 45 |
- <mail link="clement@×××××××.org">Clément Varaldi</mail> |
| 46 |
-</author> |
| 47 |
-<author title="Editor"> |
| 48 |
- <mail link="robin.perkins@××××××××××××.net">Robin Perkins</mail> |
| 49 |
+ <mail link="ppc-macos@g.o">PPC MacOS Team</mail> |
| 50 |
</author> |
| 51 |
|
| 52 |
<abstract> |
| 53 |
-This guide walks the average user through the installation and usage of portage |
| 54 |
-on Mac OS X. |
| 55 |
+This guide has been removed |
| 56 |
</abstract> |
| 57 |
|
| 58 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 59 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
| 60 |
<license/> |
| 61 |
|
| 62 |
-<version>1.6</version> |
| 63 |
-<date>2005-06-20</date> |
| 64 |
+<version>2.0</version> |
| 65 |
+<date>2005-11-26</date> |
| 66 |
|
| 67 |
<chapter> |
| 68 |
-<title>Installation</title> |
| 69 |
-<section> |
| 70 |
-<title>System Requirements</title> |
| 71 |
-<body> |
| 72 |
- |
| 73 |
-<p> |
| 74 |
-In order to install Gentoo for Mac OS X, you must have the following software |
| 75 |
-already installed: |
| 76 |
-</p> |
| 77 |
- |
| 78 |
-<ul> |
| 79 |
- <li>Mac OS 10.3 or later</li> |
| 80 |
- <li>XCode Tools 1.2 or later</li> |
| 81 |
-</ul> |
| 82 |
- |
| 83 |
-<note> |
| 84 |
-The XCode Tools can be downloaded at no cost from the <uri |
| 85 |
-link="https://connect.apple.com">Apple Developer Connection</uri> member site |
| 86 |
-(free membership required). |
| 87 |
-</note> |
| 88 |
- |
| 89 |
-<impo> |
| 90 |
-We <e>strongly</e> recommend that XCode be installed with the X11 SDK. |
| 91 |
-</impo> |
| 92 |
- |
| 93 |
-</body> |
| 94 |
-</section> |
| 95 |
-<section> |
| 96 |
-<title>The Installer</title> |
| 97 |
-<body> |
| 98 |
- |
| 99 |
-<p> |
| 100 |
-First, you'll need to download the <uri |
| 101 |
-link="http://www.metadistribution.org/macos">Gentoo for Mac OS X installer disk |
| 102 |
-image (dmg)</uri>. When you mount the dmg image (by double clicking on it), its |
| 103 |
-contents should be displayed on the screen in a finder window; the installer |
| 104 |
-icon should be visible at this point. Run the installer, and follow the |
| 105 |
-directions on screen. |
| 106 |
-</p> |
| 107 |
- |
| 108 |
-</body> |
| 109 |
-</section> |
| 110 |
+<title>Notice</title> |
| 111 |
<section> |
| 112 |
-<title>Terminal.app</title> |
| 113 |
<body> |
| 114 |
|
| 115 |
<p> |
| 116 |
-After the installer has finished and exited, you will need to open Terminal.app |
| 117 |
-(or another terminal emulator). If you already have Terminal.app open, you'll |
| 118 |
-need to open a new shell/window for the software installed by the installer to |
| 119 |
-be recognized by the terminal session. |
| 120 |
+This guide has been removed. Please check the <uri |
| 121 |
+link="/proj/en/gentoo-alt/macos/">Portage for Darwin/Mac OS X</uri> project |
| 122 |
+page for more information. |
| 123 |
</p> |
| 124 |
|
| 125 |
-<warn> |
| 126 |
-Using any shell besides bash is currenly unsupported and most likely won't |
| 127 |
-work. You should change your default shell in Terminal.app by clicking on |
| 128 |
-Terminal->Preferences (in the menu bar), chosing the "Execute this command" |
| 129 |
-option, and entering <c>/bin/bash</c>. |
| 130 |
-</warn> |
| 131 |
- |
| 132 |
-</body> |
| 133 |
-</section> |
| 134 |
-<section> |
| 135 |
-<title>Updating Portage</title> |
| 136 |
-<body> |
| 137 |
- |
| 138 |
-<p> |
| 139 |
-It's crucial to keep portage's package information database (commonly called |
| 140 |
-the 'portage tree') up-to-date; it lives in <path>/usr/portage</path>. The |
| 141 |
-portage tree holds information about every package that portage knows how to |
| 142 |
-install, including directions that portage follows to install the package for |
| 143 |
-you. It is important that we update this information to the latest available |
| 144 |
-tree before we continue so that we know we have all the latest information on |
| 145 |
-the latest packages. |
| 146 |
-</p> |
| 147 |
- |
| 148 |
-<p> |
| 149 |
-Once in a console, you will need to keep root privileges in order to continue. |
| 150 |
-If you are a computer administrator, this is as easy as using sudo. |
| 151 |
-</p> |
| 152 |
- |
| 153 |
-<pre caption="Getting root privileges"> |
| 154 |
-$ <i>sudo su</i> |
| 155 |
-Password: |
| 156 |
-</pre> |
| 157 |
- |
| 158 |
-<p> |
| 159 |
-To make sure that you have the latest fixes and package information available, |
| 160 |
-you'll now need to synchronize your portage tree with the latest from the gentoo |
| 161 |
-servers. |
| 162 |
-</p> |
| 163 |
- |
| 164 |
-<pre caption="Updating your portage tree"> |
| 165 |
-# <i>emerge --sync</i> |
| 166 |
-</pre> |
| 167 |
- |
| 168 |
-</body> |
| 169 |
-</section> |
| 170 |
-<section> |
| 171 |
-<title>Configuration</title> |
| 172 |
-<body> |
| 173 |
- |
| 174 |
-<p> |
| 175 |
-We now need to tell portage a little about your version of OSX. Portage uses |
| 176 |
-the files in <path>/etc/make.profile</path> to determine which packages are |
| 177 |
-already installed by Mac OS X, which packages are masked for your version of |
| 178 |
-Mac OS X, and default configuration options. You should use one of the provided |
| 179 |
-profiles, and simply provide the system with an alias from |
| 180 |
-<path>/etc/make.profile</path> to a pre-written profile. For most people, doing |
| 181 |
-this is as simple as running the bootstrap configuration script. |
| 182 |
-</p> |
| 183 |
- |
| 184 |
-<pre caption="Running the bootstrap configuration script"> |
| 185 |
-# <i>sh /usr/portage/scripts/bootstrap-macos.sh</i> |
| 186 |
-</pre> |
| 187 |
- |
| 188 |
-<p> |
| 189 |
-Should you need to link your profile manually, you can enter the command from |
| 190 |
-one of the code blocks below, choosing the one appropriate for your system. |
| 191 |
-</p> |
| 192 |
- |
| 193 |
-<pre caption="Aliasing your default profile for Jaguar/Panther"> |
| 194 |
-# <i>ln -s /usr/portage/profiles/default-darwin/macos/10.3 /etc/make.profile</i> |
| 195 |
-</pre> |
| 196 |
- |
| 197 |
-<pre caption="Aliasing your default profile for Tiger"> |
| 198 |
-# <i>ln -s /usr/portage/profiles/default-darwin/macos/10.4 /etc/make.profile</i> |
| 199 |
-</pre> |
| 200 |
- |
| 201 |
-<note> |
| 202 |
-Advanced users can also venture to further configure portage by specifying |
| 203 |
-configuration options in <path>/etc/make.conf</path>. This is not recommended |
| 204 |
-for the average user. |
| 205 |
-</note> |
| 206 |
- |
| 207 |
-</body> |
| 208 |
-</section> |
| 209 |
-<section> |
| 210 |
-<title>Installing System Packages</title> |
| 211 |
-<body> |
| 212 |
- |
| 213 |
-<p> |
| 214 |
-Next, you need to 'emerge' the system. This installs other packages that |
| 215 |
-portage needs to operate correctly. |
| 216 |
-</p> |
| 217 |
- |
| 218 |
-<pre caption="Emerging system"> |
| 219 |
-# <i>emerge system</i> |
| 220 |
-</pre> |
| 221 |
- |
| 222 |
-<p> |
| 223 |
-Congratulations! Your new Gentoo for Mac OS X installation should be ready to |
| 224 |
-go. |
| 225 |
-</p> |
| 226 |
- |
| 227 |
-</body> |
| 228 |
-</section> |
| 229 |
-</chapter> |
| 230 |
- |
| 231 |
-<chapter> |
| 232 |
-<title>Installing Software Using Portage</title> |
| 233 |
- |
| 234 |
-<section> |
| 235 |
-<title>Install Software</title> |
| 236 |
-<body> |
| 237 |
- |
| 238 |
-<p> |
| 239 |
-To install a package in portage, all that needs to be done is to 'emerge' it. |
| 240 |
-Portage will take care of all the dependencies of the package. Installing a |
| 241 |
-package is easy once you know what the name of the package is. |
| 242 |
-</p> |
| 243 |
- |
| 244 |
-<pre caption="Emerging Lynx"> |
| 245 |
-# <i>emerge lynx</i> |
| 246 |
-</pre> |
| 247 |
- |
| 248 |
-</body> |
| 249 |
-</section> |
| 250 |
-<section> |
| 251 |
-<title>Masked Packages</title> |
| 252 |
-<body> |
| 253 |
- |
| 254 |
-<p> |
| 255 |
-You should be able to emerge any combination of packages that have already been |
| 256 |
-tested and updated to work with macos. Currently, only a very small number of |
| 257 |
-packages are not masked. If an ebuild hasn't had the ppc-macos keyword added to it, |
| 258 |
-you will get a message similar to the following. |
| 259 |
-</p> |
| 260 |
- |
| 261 |
-<pre caption="Example of a masked package"> |
| 262 |
-# <i>emerge -p cowsay</i> |
| 263 |
- |
| 264 |
- These are the packages that I would merge, in order: |
| 265 |
- |
| 266 |
- Calculating dependencies |
| 267 |
- !! all ebuilds that could satisfy "cowsay" have been masked. |
| 268 |
- !! possible candidates are: |
| 269 |
- - games-misc/cowsay-3.03 (masked by: missing keyword) |
| 270 |
-</pre> |
| 271 |
- |
| 272 |
-</body> |
| 273 |
-</section> |
| 274 |
-<section> |
| 275 |
-<title>Testing Packages</title> |
| 276 |
-<body> |
| 277 |
- |
| 278 |
-<p> |
| 279 |
-You might want to test a package yourself to see if it works, regardless of it's |
| 280 |
-masked state. While we do not suggest that the average user do this, people that |
| 281 |
-wish to help the developers in testing packages are free to unmask and test |
| 282 |
-packages on their system. This is done by adding the 'ppc-macos' keyword to an |
| 283 |
-package information file, or 'ebuild'. To add the ppc-macos keyword to an ebuild, |
| 284 |
-you use the 'ekeyword' command, which is part of the the gentoolkit-dev package. |
| 285 |
-</p> |
| 286 |
- |
| 287 |
-<pre caption="Installing gentoolkit-dev"> |
| 288 |
-# <i>emerge gentoolkit-dev</i> |
| 289 |
-</pre> |
| 290 |
- |
| 291 |
-<pre caption="Keywording a package"> |
| 292 |
-# <i>cd /usr/portage/games-misc/cowsay</i> |
| 293 |
-# <i>ekeyword ppc-macos cowsay-3.03.ebuild</i> |
| 294 |
-# <i>ebuild cowsay-3.03.ebuild digest</i> |
| 295 |
-</pre> |
| 296 |
- |
| 297 |
-<p> |
| 298 |
-If the package successfully compiles and runs properly, please submit a bug to |
| 299 |
-<uri link="http://bugs.gentoo.org">Gentoo Bugzilla</uri> (free membership |
| 300 |
-required) notifying us that the package works (feel free to assign the bug to |
| 301 |
-the Gentoo for Mac OS X developer team, osx@g.o). If it doesn't work, |
| 302 |
-submit a bug that shows us the error(s) you received (usually there are a great |
| 303 |
-deal of errors; copy and paste from the first message that looks like an error |
| 304 |
-until the end of the output). |
| 305 |
-</p> |
| 306 |
- |
| 307 |
-<p> |
| 308 |
-For most packages that require X11 to run, you will need to install the X11 |
| 309 |
-development package. If you did not opt to install this during the XCode |
| 310 |
-install, you can install it easily afterwards from the <path>X11SDK.pkg</path> |
| 311 |
-file, found in the <path>Packages</path> directory of your Xcode 1.2 CD (simply |
| 312 |
-double-click to install). You should not yet try to emerge portage from the |
| 313 |
-ebuilds. There is a <uri link="#portage-dep">workaround</uri> for packages |
| 314 |
-that depend on portage (such as gentoolkit). |
| 315 |
-</p> |
| 316 |
- |
| 317 |
-<warn> |
| 318 |
-The "macos" keyword is obsolete and should not be used anymore. |
| 319 |
-</warn> |
| 320 |
- |
| 321 |
-</body> |
| 322 |
-</section> |
| 323 |
-<section> |
| 324 |
-<title>Already Installed Packages</title> |
| 325 |
-<body> |
| 326 |
- |
| 327 |
-<p> |
| 328 |
-If you find a package that is already installed by Mac OS X, you should file a |
| 329 |
-bug on <uri link="http://bugs.gentoo.org">Gentoo Bugzilla</uri> (free membership |
| 330 |
-required). On your own system, you can add a package to |
| 331 |
-<path>/etc/portage/profile/package.provided</path> so that portage realizes |
| 332 |
-that the package is installed. |
| 333 |
-</p> |
| 334 |
- |
| 335 |
-<pre caption="Adding a package to package.provided"> |
| 336 |
-# <i>mkdir -p /etc/portage/profile/</i> |
| 337 |
-# <i>echo cat-name/package-x.y.z >> /etc/portage/profile/package.provided</i> |
| 338 |
-</pre> |
| 339 |
- |
| 340 |
-<note> |
| 341 |
-To see a list of packages that the developers have deemed as pre-installed by |
| 342 |
-Apple on your version of Mac OS X, you may consult |
| 343 |
-<path>/etc/make.profile/package.provided</path>. |
| 344 |
-</note> |
| 345 |
- |
| 346 |
-<warn> |
| 347 |
-Modifying <path>/etc/make.profile/package.provided</path> is not recommended, |
| 348 |
-as it will be overwritten every time the portage tree is updated (using 'emerge |
| 349 |
---sync') |
| 350 |
-</warn> |
| 351 |
- |
| 352 |
-</body> |
| 353 |
-</section> |
| 354 |
-</chapter> |
| 355 |
- |
| 356 |
-<chapter> |
| 357 |
-<title>Using CVS</title> |
| 358 |
-<section> |
| 359 |
-<title>Problems with case sensitivity</title> |
| 360 |
-<body> |
| 361 |
- |
| 362 |
-<p> |
| 363 |
-The scripts in CVS have problems with case-insensitive file systems like HFS(+), |
| 364 |
-so you will need to create a case-sensitive file system image (we recommend at |
| 365 |
-least 750MB in size) onto which you may check out the CVS portage tree. Either |
| 366 |
-of the following commands can be used to create such a file system image: |
| 367 |
-</p> |
| 368 |
- |
| 369 |
-<pre caption="Creating a case-sensitive UFS image"> |
| 370 |
-<comment>(Replace 'gentoo-cvs.dmg' with the desired filename,</comment> |
| 371 |
-<comment>and 'Gentoo-CVS' with the desired volume name.)</comment> |
| 372 |
-$ <i>hdiutil create -size 750m gentoo-cvs.dmg -volname Gentoo-CVS -fs UFS</i> |
| 373 |
-</pre> |
| 374 |
- |
| 375 |
-<pre caption="Creating a case-sensitive HFS+ image"> |
| 376 |
-<comment>Replace 'gentoo-cvs.dmg' with the desired filename,</comment> |
| 377 |
-<comment>and 'Gentoo-CVS' with the desired volume name.</comment> |
| 378 |
-$ <i>hdiutil create -size 750m gentoo-cvs.dmg -volname Gentoo-CVS -fs HFSX</i> |
| 379 |
-</pre> |
| 380 |
- |
| 381 |
-<warn> |
| 382 |
-Developers: repoman will not work with spaces in the path to the portage tree |
| 383 |
-root; you should not use spaces in the volume name for your CVS image. |
| 384 |
-</warn> |
| 385 |
- |
| 386 |
-</body> |
| 387 |
-</section> |
| 388 |
-</chapter> |
| 389 |
- |
| 390 |
-<chapter> |
| 391 |
-<title>Uninstallation</title> |
| 392 |
- |
| 393 |
-<section> |
| 394 |
-<title>Uninstall Script</title> |
| 395 |
-<body> |
| 396 |
- |
| 397 |
-<p> |
| 398 |
-To uninstall Gentoo for Mac OS X, you can use the |
| 399 |
-<uri link="http://dev.gentoo.org/~alexander/files/uninstall.pl">uninstall |
| 400 |
-script</uri>, which allows you to choose whether or not you would like to |
| 401 |
-unmerge the packages you installed with Gentoo for MacOS. |
| 402 |
-</p> |
| 403 |
- |
| 404 |
-<pre caption="Uninstalling Gentoo for Mac OS X"> |
| 405 |
-# <i>sudo perl uninstall.pl</i> |
| 406 |
-</pre> |
| 407 |
- |
| 408 |
-<note> |
| 409 |
-To uninstall, you should run the script with root privileges. |
| 410 |
-</note> |
| 411 |
- |
| 412 |
-</body> |
| 413 |
-</section> |
| 414 |
-</chapter> |
| 415 |
- |
| 416 |
-<chapter> |
| 417 |
-<title>Available Packages</title> |
| 418 |
- |
| 419 |
-<section> |
| 420 |
-<title>Overview</title> |
| 421 |
-<body> |
| 422 |
- |
| 423 |
-<p> |
| 424 |
-There are several ways to view a list of packages that have been marked with the |
| 425 |
-'ppc-macos' keyword, and are therefore marked as stable on Mac OS X. Since there is |
| 426 |
-so much current development on marking packages as stable on Gentoo for Mac OS |
| 427 |
-X, users are encouraged to check the list of available packages frequently. |
| 428 |
-</p> |
| 429 |
- |
| 430 |
-</body> |
| 431 |
-</section> |
| 432 |
-<section> |
| 433 |
-<title>Gentoo Fresh Mac OS X Ebuilds</title> |
| 434 |
-<body> |
| 435 |
- |
| 436 |
-<p> |
| 437 |
-The <uri link="http://packages.gentoo.org/archs/ppc-macos/stable/">Gentoo Linux |
| 438 |
-Fresh Mac OS X Ebuilds</uri> site is part of the official <uri |
| 439 |
-link="http://packages.gentoo.org">Fresh Gentoo Ebuilds</uri> site. It not only |
| 440 |
-lists current ebuild information, but also allows searching, and offers an even |
| 441 |
-more popular feature, RSS feeds (even on a per-keyword basis). There is an <uri |
| 442 |
-link="http://packages.gentoo.org/archs/ppc-macos/stable/gentoo_simple.rss">RSS feed |
| 443 |
-for the latest ebuilds keyworded 'ppc-macos'</uri> available on the <uri |
| 444 |
-link="http://packages.gentoo.org/feeds">Fresh Gentoo Ebuilds Feeds List</uri>. |
| 445 |
-</p> |
| 446 |
- |
| 447 |
-</body> |
| 448 |
-</section> |
| 449 |
-<section> |
| 450 |
-<title>Gentoo-Portage.com</title> |
| 451 |
-<body> |
| 452 |
- |
| 453 |
-<p> |
| 454 |
-<uri link="http://www.gentoo-portage.com">Gentoo-Portage.com</uri> is an |
| 455 |
-unoffical source for portage tree information, much like |
| 456 |
-<uri link="http://packages.gentoo.org">Fresh Gentoo Ebuilds</uri>, but offers |
| 457 |
-more features on a per-ebuild information basis, such as reverse dependencies |
| 458 |
-per package, etc. |
| 459 |
-</p> |
| 460 |
- |
| 461 |
-</body> |
| 462 |
-</section> |
| 463 |
-</chapter> |
| 464 |
- |
| 465 |
-<chapter> |
| 466 |
-<title>Advanced Features, & Troubleshooting</title> |
| 467 |
- |
| 468 |
-<section> |
| 469 |
-<title>Collision Protection</title> |
| 470 |
-<body> |
| 471 |
- |
| 472 |
-<p> |
| 473 |
-Gentoo for MacOS features automatic collision protection that prevents portage |
| 474 |
-from overwriting files that it did not previously put there itself. This can be |
| 475 |
-turned off with <c>FEATURES="-collision-protect"</c>. |
| 476 |
-</p> |
| 477 |
- |
| 478 |
-<pre caption="Allowing portage to overwrite Mac OS X files"> |
| 479 |
-# <i>FEATURES="-collision-protect" emerge autoconf</i> |
| 480 |
-</pre> |
| 481 |
- |
| 482 |
-<warn> |
| 483 |
-Disabling collision protection is <e>very</e> dangerous and can yield a |
| 484 |
-nonworking system. |
| 485 |
-</warn> |
| 486 |
- |
| 487 |
-</body> |
| 488 |
-</section> |
| 489 |
-<section> |
| 490 |
-<title>emerge: command not found</title> |
| 491 |
-<body> |
| 492 |
- |
| 493 |
-<p> |
| 494 |
-The Gentoo for Mac OSX installer updates the <path>/etc/profile</path> file by |
| 495 |
-adding <path>/usr/lib/portage/bin</path> to your <c>PATH</c> environment |
| 496 |
-variable. In order to simply run <c>emerge ...</c>, you may need to type source |
| 497 |
-<path>/etc/profile</path> or log out and log back in in order to avoid having to |
| 498 |
-type the full path <path>/usr/lib/portage/bin/<toolname></path>) to run |
| 499 |
-Portage tools. |
| 500 |
-</p> |
| 501 |
- |
| 502 |
-</body> |
| 503 |
-</section> |
| 504 |
-<section> |
| 505 |
-<title>Errors with <library>.a</title> |
| 506 |
-<body> |
| 507 |
- |
| 508 |
-<p> |
| 509 |
-When installing <path><library>.a</path> files, ranlib is run to ensure |
| 510 |
-that the library references appropriate paths. When <c>make install</c> is |
| 511 |
-executed in an ebuild, things are actually installed to <path>/var/tmp/portage |
| 512 |
-<package>/image</path> rather than the actual live filesystem (livefs). |
| 513 |
-This means that libraries installed by the ebuild reference incorrect paths. |
| 514 |
-This problem only exists on the darwin kernel with it's |
| 515 |
-<path><library>.a</path> files, and is being worked on by the Gentoo for |
| 516 |
-Mac OS X team. |
| 517 |
-</p> |
| 518 |
- |
| 519 |
-<p> |
| 520 |
-According to Gentoo for Mac OS X policy, ebuilds that install libraries must be |
| 521 |
-checked to be in working order before they are keyworded as 'ppc-macos'. Most of the |
| 522 |
-time, the reason that the libraries are nonworking is that the libary simply |
| 523 |
-references incorrect paths. For the adventurers out there, there's a simple |
| 524 |
-workaround for this. The <c>ranlib</c> command fixes, amongst other things, |
| 525 |
-references to incorrect paths in libraries. |
| 526 |
-</p> |
| 527 |
- |
| 528 |
-<pre caption="Using ranlib to fix broken libraries"> |
| 529 |
-<comment>(Replace '/usr/lib/libjpeg.a' with the broken library)</comment> |
| 530 |
-# <i>ranlib /usr/lib/libjpeg.a</i> |
| 531 |
-</pre> |
| 532 |
- |
| 533 |
-</body> |
| 534 |
-</section> |
| 535 |
-<section id="portage-dep"> |
| 536 |
-<title>The portage dependency</title> |
| 537 |
-<body> |
| 538 |
- |
| 539 |
-<p> |
| 540 |
-Some packages depend on portage being installed. There is currently a problem |
| 541 |
-with portage not knowing that it is installed. While the Gentoo for OS X team |
| 542 |
-works on this bug, there is a simple workaround. It is possible to attempt to |
| 543 |
-emerge any package without emerging its dependencies. This can be used to get |
| 544 |
-around the portage dependency, but should never be used for any other |
| 545 |
-dependency. |
| 546 |
-</p> |
| 547 |
- |
| 548 |
-<pre caption="Disregarding dependencies during an emerge"> |
| 549 |
-# <i>emerge --nodeps gentoolkit</i> |
| 550 |
-</pre> |
| 551 |
- |
| 552 |
</body> |
| 553 |
</section> |
| 554 |
</chapter> |
| 555 |
|
| 556 |
|
| 557 |
|
| 558 |
1.120 +2 -7 xml/htdocs/doc/en/metadoc.xml |
| 559 |
|
| 560 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.120&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 561 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.120&content-type=text/plain&cvsroot=gentoo |
| 562 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml.diff?r1=1.119&r2=1.120&cvsroot=gentoo |
| 563 |
|
| 564 |
Index: metadoc.xml |
| 565 |
=================================================================== |
| 566 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v |
| 567 |
retrieving revision 1.119 |
| 568 |
retrieving revision 1.120 |
| 569 |
diff -u -r1.119 -r1.120 |
| 570 |
--- metadoc.xml 16 Nov 2005 15:47:23 -0000 1.119 |
| 571 |
+++ metadoc.xml 26 Nov 2005 00:12:31 -0000 1.120 |
| 572 |
@@ -1,9 +1,9 @@ |
| 573 |
<?xml version='1.0' encoding="UTF-8"?> |
| 574 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.119 2005/11/16 15:47:23 neysx Exp $ --> |
| 575 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.120 2005/11/26 00:12:31 neysx Exp $ --> |
| 576 |
<!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd"> |
| 577 |
|
| 578 |
<metadoc lang="en"> |
| 579 |
-<version>1.48</version> |
| 580 |
+<version>1.49</version> |
| 581 |
<members> |
| 582 |
<lead>swift</lead> |
| 583 |
<lead>neysx</lead> |
| 584 |
@@ -275,7 +275,6 @@ |
| 585 |
<file id="gentoo-sparc-obpreference">/doc/en/gentoo-sparc-obpreference.xml</file> |
| 586 |
<file id="gnome-config">/doc/en/gnome-config.xml</file> |
| 587 |
<file id="gpm">/doc/en/gpm.xml</file> |
| 588 |
- <file id="macos-guide">/doc/en/macos-guide.xml</file> |
| 589 |
<file id="gentoo-security">/doc/en/gentoo-security.xml</file> |
| 590 |
<file id="home-router-howto">/doc/en/home-router-howto.xml</file> |
| 591 |
<file id="arm-requirements">/doc/en/arm-requirements.xml</file> |
| 592 |
@@ -659,10 +658,6 @@ |
| 593 |
<memberof>gentoo_portage</memberof> |
| 594 |
<fileid>gentoolkit</fileid> |
| 595 |
</doc> |
| 596 |
- <doc id="macos-guide"> |
| 597 |
- <memberof>gentoo_portage</memberof> |
| 598 |
- <fileid>macos-guide</fileid> |
| 599 |
- </doc> |
| 600 |
<doc id="environment-variables"> |
| 601 |
<memberof>gentoo_configuring</memberof> |
| 602 |
<fileid vpart="2" vchap="5">handbook-x86</fileid> |
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
-- |
| 607 |
gentoo-doc-cvs@g.o mailing list |
Archives