From mark.round at gmail.com Tue Nov 1 12:22:29 2005 From: mark.round at gmail.com (Mark Round) Date: Tue, 1 Nov 2005 11:22:29 +0000 Subject: [csw-announce] New PHP 4.4.0 packages Message-ID: <7b46f0de0511010322g2b8afa2bre81cebd19df3e181@mail.gmail.com> New PHP 4.4.0 packages are now available from the mirror sites. There are a number of changes with these packages over previous 4.3.x packages - please make sure you read the following to find out how this move will affect your installation. 1. Changes in packaging 1.1 Modular extensions The PHP packages now include a very minimal "core". Many extensions are now built as shared libraries and have been split off into their own packages. The reasoning behind this is that a user can just grab what they need, instead of a huge monolithic build of PHP that eats up memory with things that they very probably don't need - not to mention saving space and time by not downloading all the various dependencies that go with it. Under this new system, if you just want PHP with, say MySQL and OpenSSL support, you would install the core PHP package (and optionally, the mod_php Apache extension) then php4_mysql and php4_openssl. 1.2 Multiple SAPIs, Apache 2 support, standalone CGI package As a user may just want the CLI or CGI executables, these are now shipped in the core php4_cgi package, which all other PHP4 packages now depend on. This includes the binaries, PEAR libraries, and various headers. It also takes care of installing a php.ini, if none exists. This is also the package you'd use if you wanted to set up a FastCGI environment. If you actually want mod_php for either Apache 1.3.x or 2.0.x, you'd install mod_php4_core (CSWmodphp4). This includes a dependency on php4_cgi, so if you install this, you'll also get the PEAR libraries and "foundations" needed for PHP to function etc. It now includes an Apache 2 module shipped alongside the standard Apache 1. These have both been relocated to /opt/csw/lib/php/sapi. The postinstall script will check for the presence of CSWapache or CSWapache2, and if found, will activate itself. As long as both servers are listening on different ports, you can even run both on the same machine. The big caveat here is that if you are using Apache 2 and PHP, you should only ever use the prefork MPM. There is also a "bundle" package, mod_php (CSWphp), which now doesn't contain any files, but does contain dependencies for php4_cgi, mod_php4_core, apache 1.3.x, and all the extensions. This emulates the behavious of the old monolithic CSWphp build; for a full PHP4 installation, this is the package you'd install (pkg-get -i php). 2. Upgrading a current installation If you are using a current CSWphp installation, upgrade your catalog, and then upgrade the "mod_php" package. This will then upgrade your mod_php to the new dummy build, and install the core php4_cgi and mod_php4_core packages, along with all extensions. This will however leave you with a full PHP installation, and you may then want to uninstall some of the PHP extensions you are not using. -Mark mark at blastwave.org From pfelecan at blastwave.org Wed Nov 2 09:17:34 2005 From: pfelecan at blastwave.org (Peter FELECAN) Date: Wed, 02 Nov 2005 09:17:34 +0100 Subject: [csw-announce] The GNU Compiler Collection 4.0.2 is released as Blastwave packages Message-ID: The maintenance release of the new GNU Compiler Collection is available. This is the branch 4 of the GNU compiler suite. The branch 4 is new. My recommendation is to not use it in a production environment. If you wish to use a stable and well tested version of the GNU compiler suite you can use the branch 3; for this, look for the gcc3 related packages. There is also the branch 2 which is still used and sometimes preferred for some products. If you are in this situation look for the gcc2 related packages. Some relevant notes: 1. The branch 4 compiler is installed in /opt/csw/gcc4, similar to the branch 2 and 3, and the rt packages install the versioned shared libraries in /opt/csw/gcc4/lib. Note: gcc3 packages install their shared libraries in /opt/csw/lib. 2. There is a fixinclude stage executed in the postinstall script for gcc4core. [see point 6 in the notes at the end of this document] 3. The granularity of the packages is identical to that of the FSF, i.e. gcc4core, gcc4g++, gcc4g95, gcc4java, gcc4objc, gcc4ada and each one has a corresponding runtime package, e.g. gcc4corert; a similar granularity can be found in the branch 2 and 3. gcc4core C compiler gcc4g++ C++ compiler gcc4g95 FORTRAN 95 compiler gcc4java Java compiler gcc4objc Objective C compiler gcc4ada Ada Compiler 4. The packages inter-dependencies are as follows: gcc4corert: gcc4core: \ gcc4corert gcc4g++rt: \ gcc4corert gcc4g++: \ gcc4core \ gcc4g++rt gcc4g95rt: \ gcc4corert gcc4g95: \ gcc4core \ gcc4g95rt gcc4javart: \ gcc4corert gcc4java: \ gcc4core gcc4javart gcc4objcrt: \ gcc4corert gcc4objc: \ gcc4core \ gcc4objcrt gcc4adart:\ gcc4corert gcc4ada: \ gcc4core \ gcc4adart 5. All the packages were tested using the latest testsuite (4.0), with the exception of Java which doesn't have a test set, on Solaris SPARC 9 and Solaris Intel 8 It should also be noted that: 1. /opt/csw has precedence in searching headers, libraries and dynamic libraries. 2. /usr/local/include or /opt/sfw/include are not part of the default include search path. 3. There is no dependency on 4. -mcpu=v8 is the default on SPARC (instead of -mcpu=v7) 5. Each package has its documentation in a specific directory in /opt/csw/share/doc, the common documents are linked to the gcc4core directory, and additionally contains the documentation in PostScript and PDF. 6. The includes need fixing each time that the system includes are updated. Consequently, there is the possibility to fix the system includes when needed by running the following script, as root: /opt/csw/gcc4/bin/mkheaders 7. The documentation in info format is stored in /opt/csw/gcc4/info. If you wish to access it from info aware tools, add this directory to the INFOPATH environment variable. For example, for a bash user: export INFOPATH=/opt/csw/info:/opt/csw/gcc4/info Those interested by the QA and the test results for this release, are invited to read http://pfelecan.free.fr/blastwave/gcc/QA/ , especially the sections concerning the embedded and external tests. -- Peter From mark at markround.com Tue Nov 15 08:21:54 2005 From: mark at markround.com (Mark Round) Date: Tue, 15 Nov 2005 07:21:54 +0000 Subject: [csw-announce] New postgresql 8.1.0 packages available Message-ID: I'm pleased to announce that PostgreSQL 8.1.0 packages are now available from Blastwave, and should be making their way out to the mirrors as I type. This set of packages includes libpq, the core postgresql package, contrib, and the updated set of JDBC drivers. Please note that there are a large number of changes with this 8.1.0 release - for details on all the new features, please see the official PostgreSQL announcement : http://www.postgresql.org/docs/ whatsnew . Please also note that if you are intending to update to this version from a previous installation (either 7.3.x or 8.0.x), you will need to do a dump and reload of your database. Your old data directory will not work with the new packages, due to changes made by the PostgreSQL developers. For information on this dump and reload procedure, see the HTML documentation (also included with the package) at the following URL : http://www.postgresql.org/docs/8.1/ interactive/backup.html . I recommend taking a full dump of your database and testing the backup works as expected before proceeding with this upgrade. All comments, bug reports, feedback etc. welcome. -Mark mark at blastwave.org From mark.round at gmail.com Tue Nov 1 12:22:29 2005 From: mark.round at gmail.com (Mark Round) Date: Tue, 1 Nov 2005 11:22:29 +0000 Subject: [csw-announce] New PHP 4.4.0 packages Message-ID: <7b46f0de0511010322g2b8afa2bre81cebd19df3e181@mail.gmail.com> New PHP 4.4.0 packages are now available from the mirror sites. There are a number of changes with these packages over previous 4.3.x packages - please make sure you read the following to find out how this move will affect your installation. 1. Changes in packaging 1.1 Modular extensions The PHP packages now include a very minimal "core". Many extensions are now built as shared libraries and have been split off into their own packages. The reasoning behind this is that a user can just grab what they need, instead of a huge monolithic build of PHP that eats up memory with things that they very probably don't need - not to mention saving space and time by not downloading all the various dependencies that go with it. Under this new system, if you just want PHP with, say MySQL and OpenSSL support, you would install the core PHP package (and optionally, the mod_php Apache extension) then php4_mysql and php4_openssl. 1.2 Multiple SAPIs, Apache 2 support, standalone CGI package As a user may just want the CLI or CGI executables, these are now shipped in the core php4_cgi package, which all other PHP4 packages now depend on. This includes the binaries, PEAR libraries, and various headers. It also takes care of installing a php.ini, if none exists. This is also the package you'd use if you wanted to set up a FastCGI environment. If you actually want mod_php for either Apache 1.3.x or 2.0.x, you'd install mod_php4_core (CSWmodphp4). This includes a dependency on php4_cgi, so if you install this, you'll also get the PEAR libraries and "foundations" needed for PHP to function etc. It now includes an Apache 2 module shipped alongside the standard Apache 1. These have both been relocated to /opt/csw/lib/php/sapi. The postinstall script will check for the presence of CSWapache or CSWapache2, and if found, will activate itself. As long as both servers are listening on different ports, you can even run both on the same machine. The big caveat here is that if you are using Apache 2 and PHP, you should only ever use the prefork MPM. There is also a "bundle" package, mod_php (CSWphp), which now doesn't contain any files, but does contain dependencies for php4_cgi, mod_php4_core, apache 1.3.x, and all the extensions. This emulates the behavious of the old monolithic CSWphp build; for a full PHP4 installation, this is the package you'd install (pkg-get -i php). 2. Upgrading a current installation If you are using a current CSWphp installation, upgrade your catalog, and then upgrade the "mod_php" package. This will then upgrade your mod_php to the new dummy build, and install the core php4_cgi and mod_php4_core packages, along with all extensions. This will however leave you with a full PHP installation, and you may then want to uninstall some of the PHP extensions you are not using. -Mark mark at blastwave.org From pfelecan at blastwave.org Wed Nov 2 09:17:34 2005 From: pfelecan at blastwave.org (Peter FELECAN) Date: Wed, 02 Nov 2005 09:17:34 +0100 Subject: [csw-announce] The GNU Compiler Collection 4.0.2 is released as Blastwave packages Message-ID: The maintenance release of the new GNU Compiler Collection is available. This is the branch 4 of the GNU compiler suite. The branch 4 is new. My recommendation is to not use it in a production environment. If you wish to use a stable and well tested version of the GNU compiler suite you can use the branch 3; for this, look for the gcc3 related packages. There is also the branch 2 which is still used and sometimes preferred for some products. If you are in this situation look for the gcc2 related packages. Some relevant notes: 1. The branch 4 compiler is installed in /opt/csw/gcc4, similar to the branch 2 and 3, and the rt packages install the versioned shared libraries in /opt/csw/gcc4/lib. Note: gcc3 packages install their shared libraries in /opt/csw/lib. 2. There is a fixinclude stage executed in the postinstall script for gcc4core. [see point 6 in the notes at the end of this document] 3. The granularity of the packages is identical to that of the FSF, i.e. gcc4core, gcc4g++, gcc4g95, gcc4java, gcc4objc, gcc4ada and each one has a corresponding runtime package, e.g. gcc4corert; a similar granularity can be found in the branch 2 and 3. gcc4core C compiler gcc4g++ C++ compiler gcc4g95 FORTRAN 95 compiler gcc4java Java compiler gcc4objc Objective C compiler gcc4ada Ada Compiler 4. The packages inter-dependencies are as follows: gcc4corert: gcc4core: \ gcc4corert gcc4g++rt: \ gcc4corert gcc4g++: \ gcc4core \ gcc4g++rt gcc4g95rt: \ gcc4corert gcc4g95: \ gcc4core \ gcc4g95rt gcc4javart: \ gcc4corert gcc4java: \ gcc4core gcc4javart gcc4objcrt: \ gcc4corert gcc4objc: \ gcc4core \ gcc4objcrt gcc4adart:\ gcc4corert gcc4ada: \ gcc4core \ gcc4adart 5. All the packages were tested using the latest testsuite (4.0), with the exception of Java which doesn't have a test set, on Solaris SPARC 9 and Solaris Intel 8 It should also be noted that: 1. /opt/csw has precedence in searching headers, libraries and dynamic libraries. 2. /usr/local/include or /opt/sfw/include are not part of the default include search path. 3. There is no dependency on 4. -mcpu=v8 is the default on SPARC (instead of -mcpu=v7) 5. Each package has its documentation in a specific directory in /opt/csw/share/doc, the common documents are linked to the gcc4core directory, and additionally contains the documentation in PostScript and PDF. 6. The includes need fixing each time that the system includes are updated. Consequently, there is the possibility to fix the system includes when needed by running the following script, as root: /opt/csw/gcc4/bin/mkheaders 7. The documentation in info format is stored in /opt/csw/gcc4/info. If you wish to access it from info aware tools, add this directory to the INFOPATH environment variable. For example, for a bash user: export INFOPATH=/opt/csw/info:/opt/csw/gcc4/info Those interested by the QA and the test results for this release, are invited to read http://pfelecan.free.fr/blastwave/gcc/QA/ , especially the sections concerning the embedded and external tests. -- Peter From mark at markround.com Tue Nov 15 08:21:54 2005 From: mark at markround.com (Mark Round) Date: Tue, 15 Nov 2005 07:21:54 +0000 Subject: [csw-announce] New postgresql 8.1.0 packages available Message-ID: I'm pleased to announce that PostgreSQL 8.1.0 packages are now available from Blastwave, and should be making their way out to the mirrors as I type. This set of packages includes libpq, the core postgresql package, contrib, and the updated set of JDBC drivers. Please note that there are a large number of changes with this 8.1.0 release - for details on all the new features, please see the official PostgreSQL announcement : http://www.postgresql.org/docs/ whatsnew . Please also note that if you are intending to update to this version from a previous installation (either 7.3.x or 8.0.x), you will need to do a dump and reload of your database. Your old data directory will not work with the new packages, due to changes made by the PostgreSQL developers. For information on this dump and reload procedure, see the HTML documentation (also included with the package) at the following URL : http://www.postgresql.org/docs/8.1/ interactive/backup.html . I recommend taking a full dump of your database and testing the backup works as expected before proceeding with this upgrade. All comments, bug reports, feedback etc. welcome. -Mark mark at blastwave.org