Changeset 78d0e3c
- Timestamp:
- 08/04/2004 05:51:45 AM (20 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 6da4d5a6
- Parents:
- 95c3dc2
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
content/databases/postgresql.xml
r95c3dc2 r78d0e3c 8 8 <!ENTITY postgresql-download-ftp "ftp://ftp.fr.postgresql.org/v&postgresql-version;/postgresql-&postgresql-version;.tar.bz2"> 9 9 <!ENTITY postgresql-size "9.7 MB"> 10 <!ENTITY postgresql-buildsize " 80MB">10 <!ENTITY postgresql-buildsize "197 MB"> 11 11 <!ENTITY postgresql-time "1.21 SBU"> 12 12 ]> … … 17 17 18 18 <sect2> 19 <title>Introduction to <application>Postgre<acronym>SQL</acronym></application></title> 20 21 <para><application>Postgre<acronym>SQL</acronym></application> is an advanced object-relational 22 database management system (<acronym>ORDBMS</acronym>), derived from the 23 Berkeley Postgres database management system.</para> 19 <title>Introduction to <application>Postgre<acronym>SQL</acronym></application> 20 </title> 21 22 <para><application>Postgre<acronym>SQL</acronym></application> is an advanced 23 object-relational database management system (<acronym>ORDBMS</acronym>), 24 derived from the Berkeley Postgres database management system.</para> 24 25 25 26 <sect3><title>Package information</title> … … 32 33 </sect3> 33 34 34 <sect3><title><application>Postgre<acronym>SQL</acronym></application> dependencies</title> 35 <sect3><title><application>Postgre<acronym>SQL</acronym></application> 36 dependencies</title> 35 37 <sect4><title>Optional</title> 36 38 <para> … … 40 42 <xref linkend="openssl"/>, 41 43 <xref linkend="Linux_PAM"/>, 44 <xref linkend="opensp"/>, 45 <xref linkend="openjade"/>, 46 <xref linkend="perl-modules"/>: SGMLSpm-&SGMLSpm-version;, 42 47 <ulink url="http://www.pdc.kth.se/kth-krb/">krb4</ulink>, 43 48 <xref linkend="mitkrb"/> or <xref linkend="heimdal"/>, … … 50 55 51 56 <sect2> 52 <title>Installation of <application>Postgre<acronym>SQL</acronym></application></title> 53 54 <para>Install <application>Postgre<acronym>SQL</acronym></application> with the following commands: </para> 57 <title>Installation of <application>Postgre<acronym>SQL</acronym></application> 58 </title> 59 60 <para>Install <application>Postgre<acronym>SQL</acronym></application> with the 61 following commands: </para> 55 62 56 63 <screen><userinput><command>./configure --prefix=/usr && … … 105 112 <para><command>useradd -d /srv/pgsql/data postgres</command>: Add an unprivileged user to run the database server.</para> 106 113 107 <para><command>createdb test, create table t1 , insert into t1 values..., select *108 from t1</command>: Create a database, add a table to it, insert some rows into the table 109 and select them to verify that the installation is working114 <para><command>createdb test, create table t1 , insert into t1 values..., 115 select * from t1</command>: Create a database, add a table to it, insert some 116 rows into the table and select them to verify that the installation is working 110 117 properly.</para> 111 118 … … 113 120 114 121 <sect2> 115 <title>Configuring <application>Postgre<acronym>SQL</acronym></application></title> 122 <title>Configuring <application>Postgre<acronym>SQL</acronym></application> 123 </title> 116 124 117 125 <sect3> 118 126 <title>Config files</title> 119 127 120 <para><filename>$PGDATA/pg_ident.con</filename>, <filename>$PGDATA/pg_hba.conf</filename>, <filename>$PGDATA/postgresql.conf</filename></para> 121 122 <para>The <envar>PGDATA</envar> environment variable is used to distinguish database 123 clusters from one another by setting it to the value of the directory 128 <para><filename>$PGDATA/pg_ident.con</filename>, 129 <filename>$PGDATA/pg_hba.conf</filename> and 130 <filename>$PGDATA/postgresql.conf</filename></para> 131 132 <para>The <envar>PGDATA</envar> environment variable is used to distinguish 133 database clusters from one another by setting it to the value of the directory 124 134 which contains the cluster desired. The three configuration files 125 135 exist in every <filename class="directory">PGDATA/</filename> directory. … … 129 139 130 140 <para>Install the <filename>/etc/rc.d/init.d/postgresql</filename> 131 init script included in the <xref linkend="intro-important-bootscripts"/> package.</para> 132 141 init script included in the <xref linkend="intro-important-bootscripts"/> 142 package.</para> 143 133 144 <screen><userinput><command>make install-postgresql</command></userinput></screen> 134 145 … … 140 151 <title>Contents</title> 141 152 142 <para>The <application>Postgre<acronym>SQL</acronym></application> package contains143 <command>clusterdb</command>,153 <para>The <application>Postgre<acronym>SQL</acronym></application> package 154 contains <command>clusterdb</command>, 144 155 <command>createdb</command>, 145 156 <command>createlang</command>, … … 187 198 <sect3><title>createdb</title> 188 199 <para><command>createdb</command> creates a new 189 <application>Postgre<acronym>SQL</acronym></application> database.</para></sect3> 200 <application>Postgre<acronym>SQL</acronym></application> database.</para> 201 </sect3> 190 202 191 203 <sect3><title>createlang</title> … … 196 208 <sect3><title>createuser</title> 197 209 <para><command>createuser</command> defines a new 198 <application>Postgre<acronym>SQL</acronym></application> user account.</para></sect3> 210 <application>Postgre<acronym>SQL</acronym></application> user account.</para> 211 </sect3> 199 212 200 213 <sect3><title>dropdb</title> 201 214 <para><command>dropdb</command> removes a 202 <application>Postgre<acronym>SQL</acronym></application> database.</para></sect3> 215 <application>Postgre<acronym>SQL</acronym></application> database.</para> 216 </sect3> 203 217 204 218 <sect3><title>droplang</title> … … 209 223 <sect3><title>dropuser</title> 210 224 <para><command>dropuser</command> removes a 211 <application>Postgre<acronym>SQL</acronym></application> user account.</para></sect3> 225 <application>Postgre<acronym>SQL</acronym></application> user account.</para> 226 </sect3> 212 227 213 228 <sect3><title>ecpg</title> 214 <para><command>ecpg</command> is the embedded <acronym>SQL</acronym> preprocessor.</para></sect3> 229 <para><command>ecpg</command> is the embedded <acronym>SQL</acronym> 230 preprocessor.</para></sect3> 215 231 216 232 <sect3><title>initdb</title> … … 222 238 223 239 <sect3><title>ipcclean</title> 224 <para><command>ipcclean</command> removes shared memory and semaphores left over by an225 aborted database server.</para></sect3>240 <para><command>ipcclean</command> removes shared memory and semaphores left 241 over by an aborted database server.</para></sect3> 226 242 227 243 <sect3><title>pg_config</title> … … 240 256 241 257 <sect3><title>pg_dump</title> 242 <para><command>pg_dump</command> dumps database data and metadata into scripts which are243 used to recreate the database.</para></sect3>258 <para><command>pg_dump</command> dumps database data and metadata into scripts 259 which are used to recreate the database.</para></sect3> 244 260 245 261 <sect3><title>pg_dumpall</title> … … 249 265 250 266 <sect3><title>pg_resetxlog</title> 251 <para><command>pg_resetxlog</command> clears the write-ahead log and optionally resets some252 fields in the <filename>pg_control</filename> file.</para></sect3>267 <para><command>pg_resetxlog</command> clears the write-ahead log and optionally 268 resets some fields in the <filename>pg_control</filename> file.</para></sect3> 253 269 254 270 <sect3><title>pg_restore</title> … … 270 286 271 287 <sect3><title>postgres</title> 272 <para><command>postgres</command> is a single user database server, generally used for273 debugging.</para></sect3>288 <para><command>postgres</command> is a single user database server, generally 289 used for debugging.</para></sect3> 274 290 275 291 <sect3><title>postmaster</title> 276 <para><command>postmaster</command> is the multi-user database daemon.</para></sect3> 292 <para><command>postmaster</command> is the multi-user database daemon.</para> 293 </sect3> 277 294 278 295 <sect3><title>psql</title> … … 280 297 281 298 <sect3><title>vacuumdb</title> 282 <para><command>vacuumdb</command> compacts databases and generates statistics for the283 query analyzer.</para></sect3>299 <para><command>vacuumdb</command> compacts databases and generates statistics 300 for the query analyzer.</para></sect3> 284 301 285 302 </sect2> -
general.ent
r95c3dc2 r78d0e3c 1 <!ENTITY day "0 3">1 <!ENTITY day "04"> 2 2 <!ENTITY month "08"> 3 3 <!ENTITY year "2004"> 4 4 <!ENTITY version "svn-&year;&month;&day;"> 5 <!ENTITY releasedate "August &day; rd, &year;">5 <!ENTITY releasedate "August &day;th, &year;"> 6 6 <!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP --> 7 7 <!ENTITY blfs-version "cvs"> <!-- cvs|[release #] --> 8 8 <!ENTITY lfs-version "testing"> <!-- stable|testing|unstable] --> 9 <!ENTITY last-commit " Tue Aug 03 23:28:00 MDT 2004"> <!-- Need to set up auto update for this -->9 <!ENTITY last-commit "Wed Aug 04 00:40:00 MDT 2004"> <!-- Need to set up auto update for this --> 10 10 11 11 <!ENTITY maintainer-fullname "Bruce Dubbs"> -
introduction/welcome/changelog.xml
r95c3dc2 r78d0e3c 19 19 <itemizedlist> 20 20 21 <listitem><para>August 4th, 2004 [randy]: Added optional dependencies to 22 PostgreSQL and Qt; added additional configuration information to Qt.</para> 23 </listitem> 24 21 25 <listitem><para>August 3rd, 2004 [dj]: Gramar cleanups in svnserver and 22 26 added note about running svnserve if unneeded. Also fixed lfs-root -
x/lib/qt.xml
r95c3dc2 r78d0e3c 9 9 <!ENTITY qt-md5sum "903cad618274ad84d7d13fd0027a6c3c"> 10 10 <!ENTITY qt-size "14 MB"> 11 <!ENTITY qt-buildsize " 165MB">11 <!ENTITY qt-buildsize "250 MB"> 12 12 <!ENTITY qt-time "21.2 SBU (full), 13.4 SBU (sub-tools)"> 13 13 ]> … … 24 24 for creating graphical applications or executing graphical applications that 25 25 are dynamically linked to the <application>Qt</application> library. One of the 26 major users of <application>Qt</application> is <application>KDE</application>.</para> 26 major users of <application>Qt</application> is <application>KDE</application>. 27 </para> 27 28 28 29 <sect3><title>Package information</title> … … 46 47 <sect4><title>Optional</title> 47 48 <para><xref linkend="nas"/>, <xref linkend="cups"/>, <xref linkend="mysql"/>, 48 <xref linkend="postgresql"/>, <ulink url="http://firebird.sourceforge.net/">Firebird</ulink>, 49 <xref linkend="postgresql"/>, <ulink url="http://sqlite.org/">SQLite</ulink>, 50 <ulink url="http://firebird.sourceforge.net/">Firebird</ulink> 49 51 and <ulink url="http://www.unixodbc.org/">unixODBC</ulink>.</para> 50 52 </sect4> … … 55 57 <title>Installation of <application>Qt</application></title> 56 58 57 <para>There are several ways to install a complicated package such as <application>Qt</application>. 58 The files are not completely position independent. Installation procedures execute the 59 program <filename>pkg-config</filename> to determine the location of package executables, libraries, 60 headers, and other files. For <application>Qt</application>, <filename>pkg-config</filename> will 61 look for the file <filename>lib/pkgconfig/qt-mt.pc</filename> which must be modified if relocating the 62 package. This file is set up correctly by the build process.</para> 63 64 <para>The default installation places the files in <filename class='directory'>/usr/local/qt/</filename>. 65 Many commercial distributions place the files in the system's 66 <filename class='directory'>/usr</filename> hierarchy. The package can also be installed 67 in an arbitrary directory.</para> 59 <para>There are several ways to install a complicated package such as 60 <application>Qt</application>. The files are not completely position 61 independent. Installation procedures execute the program 62 <command>pkg-config</command> to determine the location of package executables, 63 libraries, headers, and other files. For <application>Qt</application>, 64 <command>pkg-config</command> will look for the file 65 <filename>lib/pkgconfig/qt-mt.pc</filename> which must be modified if 66 relocating the package. This file is set up correctly by the build process. 67 </para> 68 69 <para>The default installation places the files in 70 <filename class='directory'>/usr/local/qt/</filename>. Many commercial 71 distributions place the files in the system's 72 <filename class='directory'>/usr</filename> hierarchy. The package can also be 73 installed in an arbitrary directory.</para> 68 74 69 75 <para>This section will demonstrate two different methods.</para> 70 76 71 72 <note><para>The build time for <application>Qt</application> is quite long. If you want to73 save some time and don't want the tutorials and examples, changethe first make line to:</para>77 <note><para>The build time for <application>Qt</application> is quite long. If 78 you want to save some time and don't want the tutorials and examples, change 79 the first make line to:</para> 74 80 75 81 <para><userinput><command>make sub-tools</command></userinput></para> … … 77 83 78 84 <sect3> 79 <title>Method 1 - Installing in the <filename class='directory'>/usr</filename> hierarchy</title> 85 <title>Method 1 - Installing in the 86 <filename class='directory'>/usr</filename> hierarchy</title> 80 87 81 <para>The advantage of this method is that no updates to the <filename>/etc/ld.so.conf</filename>82 or <filename>/etc/man.conf</filename> files are required. The package files 83 are distributed within several subdirectories of the <filename class='directory'>/usr</filename> 84 hierarchy. This is the method that most commercial distributions use.</para> 85 86 88 <para>The advantage of this method is that no updates to the 89 <filename>/etc/ld.so.conf</filename> or <filename>/etc/man.conf</filename> 90 files are required. The package files are distributed within several 91 subdirectories of the <filename class='directory'>/usr</filename> hierarchy. 92 This is the method that most commercial distributions use.</para> 93 87 94 <screen><userinput><command>sed -i "s:cp -f:install:" mkspecs/linux-g++/qmake.conf && 88 95 bash … … 107 114 <title>Method 2 - Installing in <filename class='directory'>/opt</filename></title> 108 115 109 <para>This is the method recommended by the <application>Qt</application> developers. It110 has the advantage of keeping all the package files consolidated in a dedicated directory 111 hierarchy. By using this method, an update can be made without overwriting a previous112 installation and users can easily revert to a previous version by changing one symbolic 113 link.</para>116 <para>This is the method recommended by the <application>Qt</application> 117 developers. It has the advantage of keeping all the package files consolidated 118 in a dedicated directory hierarchy. By using this method, an update can be made 119 without overwriting a previous installation and users can easily revert to a 120 previous version by changing one symbolic link.</para> 114 121 115 122 <para>The <application>Qt</application> developers use a default location of 116 <filename class='directory'>/usr/local/qt/</filename>, however this procedure puts the files 117 in <filename class='directory'>/opt/qt-&qt-version;/</filename> and then creates a 118 symbolic link to <filename>/opt/qt/</filename>.</para> 119 123 <filename class='directory'>/usr/local/qt/</filename>, however this procedure 124 puts the files in <filename class='directory'>/opt/qt-&qt-version;/</filename> 125 and then creates a symbolic link to <filename>/opt/qt/</filename>.</para> 120 126 121 127 <screen><userinput><command>bash … … 134 140 exit</command></userinput></screen> 135 141 136 <sect4> 137 <title>Configuration</title> 138 139 <para>For Method 2 only, update the <filename>/etc/ld.so.conf</filename> and 140 <filename>/etc/man.conf</filename> files.</para> 141 142 <note><para>If you're building <application>Qt</application> on top of 143 <acronym>LFS</acronym> >=6.0, the build will fail if you pass the 144 <option>--plugin-sql-<replaceable>[driver]</replaceable></option> switch to the 145 <command>configure</command> command.</para></note> 146 </sect3> 147 148 </sect2> 149 150 <sect2> 151 <title>Command explanations</title> 152 153 <para><command>sed -i "s:cp -f:install:" mkspecs/linux-g++/qmake.conf</command>: 154 <command>install</command> is safer than <command>cp</command> when 155 libraries are in use.</para> 156 157 <para><command>bash</command>: This command enters a sub-shell to isolate 158 environment changes.</para> 159 160 <para><command>export QTDIR=$PWD</command>: This command defines where the root 161 of the <application>Qt</application> directory is located.</para> 162 163 <para><command>export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH</command>: This 164 command allows the not yet installed <application>Qt</application> libraries to 165 be used by the not yet installed <application>Qt</application> programs.</para> 166 167 <para><command>export PATH=$PWD/bin:$PATH</command>: This command 168 allows the build process to find supporting executables.</para> 169 170 <para><parameter>-qt-gif</parameter>: This switch adds support for 171 <filename>gif</filename> files to the libraries.</para> 172 173 <para><parameter>-system-zlib -system-libpng</parameter>: This switch 174 forces the build instructions to use the shared libraries that are on your 175 system instead of creating a custom set of support libraries for these 176 functions.</para> 177 178 <para><parameter>-no-exceptions</parameter>: This switch disables 179 the exceptions coding generated by the <application>C++</application> compiler. 180 </para> 181 182 <para><parameter>-thread</parameter>: This switch adds 183 support for multi-threading.</para> 184 185 <para><command>find -type f -name Makefile | xargs sed -i 186 "s@-Wl,-rpath,/usr/lib@@g"</command>: This command removes hardcoded run-time 187 paths. Otherwise, <command>uic</command> always tries to run with 188 <application>Qt</application> libraries in <filename>/usr/lib</filename>.</para> 189 190 <para><command>ln -s libqt-mt.so /usr/lib/libqt.so</command>: This command 191 allows <command>configure</command> scripts to find a working 192 <application>Qt</application> installation.</para> 193 194 <para><command>cp -r doc/man /usr/share (or /opt/qt/doc)</command>: This command 195 installs the man pages which are missed by <command>make install</command>. 196 </para> 197 198 <para><command>cp -r examples /usr/share/doc/qt (or /opt/qt/doc)</command>: 199 This command installs the examples which are missed by 200 <command>make install</command>.</para> 201 202 <para><command>exit</command>: This command returns to the parent shell 203 and eliminates environment variables set earlier.</para> 204 205 </sect2> 206 207 <sect2> 208 <title>Configuring <application>Qt</application></title> 209 210 <sect3><title>Configuration Information</title> 211 <para>If you installed <application>Qt</application> using Method 2, you need 212 to update some configuration files so that <application>Qt</application> is 213 correctly found by other packages and system processes.</para> 214 215 <para>Update the <filename>/etc/ld.so.conf</filename> and 216 <filename>/etc/man.conf</filename> files:</para> 142 217 143 218 <screen><userinput><command>cat >> /etc/ld.so.conf << "EOF" … … 158 233 EOF</command></userinput></screen> 159 234 160 <para>Also, the <envar>QTDIR</envar> environment variable needs to be set when 161 building packages that depend on Qt. Add the following to the 162 <filename>.bash_profile</filename> initialization script for each user that 163 builds packages using the <application>Qt</application> libraries. 164 Alternatively, the variable can be set in the system wide 235 <para>Update the <envar>PKG_CONFIG_PATH</envar> environment variable in your 236 <filename>~/.bash_profile</filename> or <filename>/etc/profile</filename> with 237 the following:</para> 238 239 <screen><userinput>PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/opt/qt/lib/pkgconfig</userinput></screen> 240 241 <para>The <envar>QTDIR</envar> environment variable needs to be set when 242 building packages that depend on <application>Qt</application>. Add the 243 following to the <filename>.bash_profile</filename> initialization script for 244 each user that builds packages using the <application>Qt</application> 245 libraries. Alternatively, the variable can be set in the system wide 165 246 <filename>/etc/profile</filename> file.</para> 166 247 167 248 <screen><userinput>export QTDIR=/opt/qt</userinput></screen> 168 249 169 </sect4> 170 </sect3> 171 </sect2> 172 173 <sect2> 174 <title>Command explanations</title> 175 176 <para><command>sed -i "s:cp -f:install:" mkspecs/linux-g++/qmake.conf</command>: 177 <command>install</command> is safer than <command>cp</command> when 178 libraries are in use.</para> 179 180 <para><command>bash</command>: This command enters a sub-shell to isolate 181 environment changes.</para> 182 183 <para><command>export QTDIR=$PWD</command>: This command 184 defines where the root of the Qt directory is located.</para> 185 186 <para><command>export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH</command>: This command 187 allows the not yet installed qt libraries to be used by the not yet installed qt programs.</para> 188 189 <para><command>export PATH=$PWD/bin:$PATH</command>: This command 190 allows the build process to find supporting executables.</para> 191 192 <para><parameter>-qt-gif</parameter>: This switch adds support for gif 193 files to the libraries.</para> 194 195 <para><parameter>-system-zlib -system-libpng</parameter>: This switch 196 forces the build instructions to use the shared libraries that are on your system 197 instead of creating a custom set of support libraries for these 198 functions.</para> 199 200 <para><parameter>-no-exceptions</parameter>: This switch disables 201 the exceptions coding generated by the <application>C++</application> compiler.</para> 202 203 <para><parameter>-thread</parameter>: This switch adds 204 support for multi-threading.</para> 205 206 <para><command>find -type f -name Makefile | xargs sed -i 207 "s@-Wl,-rpath,/usr/lib@@g"</command>: This command removes hardcoded run-time 208 paths. Otherwise, <command>uic</command> always tries to run with Qt libraries 209 in <filename>/usr/lib</filename>.</para> 210 211 <para><command>ln -s libqt-mt.so /usr/lib/libqt.so</command>: This 212 command allows configure scripts 213 to find a working <application>Qt</application> installation.</para> 214 215 <para><command>cp -r doc/man /usr/share (or /opt/qt/doc)</command>: This command 216 installs the man pages which are missed by <command>make install</command>.</para> 217 218 <para><command>cp -r examples /usr/share/doc/qt (or /opt/qt/doc)</command>: This command 219 installs the examples which are missed by <command>make install</command>.</para> 220 221 <para><command>exit</command>: This command returns to the parent shell 222 and eliminates environment variables set earlier.</para> 223 224 </sect2> 225 <sect2> 226 <title>Configuring <application>Qt</application></title> 227 228 <sect3><title>Configuration Information</title> 250 <para>If you want the <application>Qt</application> executables in your shell 251 search path, update the <envar>PATH</envar> environment variable in your 252 <filename>~/.bash_profile</filename> or <filename>/etc/profile</filename> to 253 include <filename class='directory'>/opt/qt/bin</filename>.</para> 229 254 230 255 <para>As with most libraries, there is no explicit configuration to do. After … … 236 261 237 262 </sect2> 263 238 264 <sect2> 239 265 <title>Contents</title> … … 241 267 <para>The <application>Qt</application>/<application>X11</application> 242 268 library contains <acronym>API</acronym>s necessary to use 243 programs based on the Qt <acronym>GUI</acronym> toolkit.</para> 269 programs based on the <application>Qt</application> <acronym>GUI</acronym> 270 toolkit.</para> 244 271 245 272 <para>The <application>Qt</application> package contains
Note:
See TracChangeset
for help on using the changeset viewer.