Author: ranger
Date: Tue Sep  4 16:29:39 2007
New Revision: 945

URL: 
http://svn.finkproject.org/websvn/listing.php?sc=1&rev=945&repname=user%3a+ranger
Log:
fix postgresql docs so they show up no matter what you query

Modified:
    trunk/experimental/common/main/finkinfo/database/postgresql73-unified.info
    trunk/experimental/common/main/finkinfo/database/postgresql74-unified.info
    trunk/experimental/common/main/finkinfo/database/postgresql80-unified.info

Modified: 
trunk/experimental/common/main/finkinfo/database/postgresql73-unified.info
URL: 
http://svn.finkproject.org/websvn/diff.php?path=/trunk/experimental/common/main/finkinfo/database/postgresql73-unified.info&rev=945&repname=user%3a+ranger
==============================================================================
--- trunk/experimental/common/main/finkinfo/database/postgresql73-unified.info 
(original)
+++ trunk/experimental/common/main/finkinfo/database/postgresql73-unified.info 
Tue Sep  4 16:29:39 2007
@@ -323,6 +323,23 @@
        Description: upgrade package for postgresql73
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+       <<
 <<
 SplitOff4: <<
        Package: postgresql73-shlibs
@@ -342,6 +359,23 @@
        Description: upgrade package for postgresql73-ssl
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+       <<
 <<
 SplitOff7: <<
        Package: postgresql73-ssl-shlibs

Modified: 
trunk/experimental/common/main/finkinfo/database/postgresql74-unified.info
URL: 
http://svn.finkproject.org/websvn/diff.php?path=/trunk/experimental/common/main/finkinfo/database/postgresql74-unified.info&rev=945&repname=user%3a+ranger
==============================================================================
--- trunk/experimental/common/main/finkinfo/database/postgresql74-unified.info 
(original)
+++ trunk/experimental/common/main/finkinfo/database/postgresql74-unified.info 
Tue Sep  4 16:29:39 2007
@@ -364,6 +364,23 @@
        Description: upgrade package for postgresql74
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+       <<
 <<
 SplitOff4: <<
        Package: postgresql74-shlibs
@@ -383,6 +400,23 @@
        Description: upgrade package for postgresql74-ssl
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+       <<
 <<
 SplitOff7: <<
        Package: postgresql74-ssl-shlibs

Modified: 
trunk/experimental/common/main/finkinfo/database/postgresql80-unified.info
URL: 
http://svn.finkproject.org/websvn/diff.php?path=/trunk/experimental/common/main/finkinfo/database/postgresql80-unified.info&rev=945&repname=user%3a+ranger
==============================================================================
--- trunk/experimental/common/main/finkinfo/database/postgresql80-unified.info 
(original)
+++ trunk/experimental/common/main/finkinfo/database/postgresql80-unified.info 
Tue Sep  4 16:29:39 2007
@@ -374,6 +374,24 @@
        Package: postgresql80
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+
+       <<
 <<
 SplitOff4: <<
        Description: Upgrade package for PostgreSQL 8.0 development
@@ -393,6 +411,24 @@
        Package: postgresql80-ssl
        Depends: %N (>= %v-%r), fink (>= 0.26.0-1), fink-obsolete-packages
        DocFiles: COPYRIGHT HISTORY INSTALL README
+       DescUsage: <<
+The package runs initdb on installation as the user 'postgres'.
+
+The best way to run it is using the supplied pgsql.sh script, i.e.
+'sudo pgsql.sh start'.  Or, you can run
+'sudo daemonic enable %N' as root to create a
+StartupItem for it.
+
+Unless you set up admin users in the database, the easiest way to
+run psql commands with administrator access is to prefix them with
+the command "sudo -u postgres".  This will ask you your administrator
+password, and then run the command as the postgres user.
+
+For example, to create a new database, you would run:
+
+  sudo -u postgres createdb mydb
+
+       <<
 <<
 SplitOff7: <<
        Description: Upgrade package for PostgreSQL 8.0 development (SSL)


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-commits

Reply via email to