cvs: pearweb /weeklynews 20030119.en.html

From: Date: Sun, 19 Jan 2003 09:38:58 +0000
Subject: cvs: pearweb /weeklynews 20030119.en.html
Groups: php.pear.cvs 
Request: Send a blank email to pear-cvs+get-8402@lists.php.net to get a copy of this message
ssb Sun Jan 19 04:38:58 2003 EDT Modified files: /pearweb/weeklynews 20030119.en.html Log: * typo and html fixes Index: pearweb/weeklynews/20030119.en.html diff -u pearweb/weeklynews/20030119.en.html:1.7 pearweb/weeklynews/20030119.en.html:1.8 --- pearweb/weeklynews/20030119.en.html:1.7 Sun Jan 19 04:32:22 2003 +++ pearweb/weeklynews/20030119.en.html Sun Jan 19 04:38:58 2003 @@ -14,14 +14,14 @@ </p> <p> - To celebrate the fact PEAR out of beta and as of PHP 4.3 PEAR installer - is included by default, Weekly News is revived again. As a preface to - this first weekly news, please find an interwiew of Stig S. Backen, - the founder of the PEAR project.<br \><br \> - This week news include details on voting for proposed packages, + To celebrate the fact that PEAR is out of beta and as of PHP 4.3 PEAR + installer is included by default, Weekly News is revived again. As a + preface to this first weekly news, please find an interwiew of Stig S. + Bakken, the founder of the PEAR project.<br /><br /> + This week's news include details on voting for proposed packages, PEAR tutorial on Mac OS X, new phpdoc templates and missing PEAR installer from Windows binary distribution. As a time of writing there - has been eight new releases this week. + have been eight new releases this week. </p> <hr> <h2>AN INTERVIEW OF STIG BAKKEN</h2> @@ -36,20 +36,20 @@ FAST's multimedia search product. See <a target="_new" href="http://www.alltheweb.com/">www.alltheweb.com</a> (written in PHP of course) for a demonstration. -<br\> +<br /> <h3>What's PEAR ?</h3> PEAR is a PHP spin-off project that aims to provide several things:</li> - <li \>* a library of high-quality, reusable PHP code and extensions</li> - <li \>* coding guidelines that help create components with consistent APIs</li> - <li >* a packaging, distribution and installation framework for these components + <li /> a library of high-quality, reusable PHP code and extensions</li> + <li /> coding guidelines that help create components with consistent APIs</li> + <li /> a packaging, distribution and installation framework for these components The acronym stands for "PHP Extension and Application Repository". We made up the acronym before the meaning of course.</li> <h3>What's PECL</h3> PECL (the PHP Extension Code Library) is a subset of PEAR for traditional PHP extensions written in C or C++. -<br \> +<br /> <h3> What is the relation between PHP and PEAR/PECL, we have seen a lot @@ -62,7 +62,7 @@ all a project management change for PHP. Future versions of PHP will still bundle lots of extensions, they will be imported from PECL during the PHP release process and included in the release tarball. -<br \><br \> +<br /><br /> The reason we do this is to make PHP's release process manageable. Today a PHP release takes several months. By importing stable releases of extensions in PECL into the PHP source distribution, rather than having @@ -74,11 +74,11 @@ this pickling process does <i>not</i> mean that users will have no extensions bundled with PHP. PHP will still bundle exceptions, but higher quality is expected of bundled extensions in PHP 5. -<br \><br \> +<br /><br /> Also, if extensions are built shared (not compiled directly into PHP, but as dynamically loadable libraries), it will be possible to upgrade individual extensions without upgrading PHP. -<br \> +<br /> <h3> What are the differences between the core PEAR (package manager, core @@ -88,7 +88,7 @@ for the installer, and a set of packages that are of high quality and considered of common interest. The latter set of packages is the start of what hopefully will become the "PHP Foundation Classes" (PFC). -<br \> +<br /> <h3>May the package manager and the package definition may be used by any PHP developper for their project, private or commercial ? @@ -96,7 +96,7 @@ Anyone can set up their own copy of the pear.php.net web site and use it for distributing in-house PHP components. There are several projects already that are starting to use the PEAR tools for their own purposes. -<br \> +<br /> <h3> What are the next main achievements for PEAR ? @@ -113,7 +113,7 @@ the PEAR installer runs on a myriad of platforms and PHP configurations. And there is lots of work ahead in making a PHP 5 migration plan. -<br \> +<br /> <h3> More and more people are involved in the PEAR community, by adding @@ -127,7 +127,7 @@ "competing" packages find eachother quickly and find a good solution by their own initiative. My own role is just to nudge the community in the right direction from time to time. -<br \> +<br /> <hr> <h2>PEAR-DEV traffic</h2>

« previous php.pear.cvs (#8402) next »