Updated documentation on .pypirc support for credentials.

1 files changed, 8 insertions, 23 deletions

diff --git a/docs/easy_install.txt b/docs/easy_install.txt
index ffe6a268..a56dee49 100644
--- a/docs/easy_install.txt
+++ b/docs/easy_install.txt
@@ -454,30 +454,15 @@ You can do this with both index page URLs and direct download URLs.  As long
 as any HTML pages read by easy_install use *relative* links to point to the
 downloads, the same user ID and password will be used to do the downloading.
 
-Authentication against privat repository
-----------------------------------------
-
-To get these things running. You need a .pypirc file in your home directory. The file should has the following format.
-
-Example
-
-::
-
-    [distutils]
-    index-servers = myrepos
-
-    [myrepos]
-    repository: http://myrepos.com
-    username:MY_USER
-    password:MY_PASSORD
-
-In your buildout.cfg you have to add the eggserver url under find-links. The example is for an mypypi egg server. /eggs provides a flat package list.
-
-Example
-
-::
+Using .pypirc Credentials
+-------------------------
 
-    find-links = http://myrepos.com/eggs
+In additional to supplying credentials in the URL, ``easy_install`` will also
+honor credentials if present in the .pypirc file. Teams maintaining a private
+repository of packages may already have defined access credentials for
+uploading packages according to the distutils documentation. ``easy_install``
+will attempt to honor those if present. Refer to the distutils documentation
+for Python 2.5 or later for details on the syntax.
 
 Controlling Build Options
 ~~~~~~~~~~~~~~~~~~~~~~~~~