Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://anil.recoil.org/notes/php-port-layout-openbsd",
3 "title": "Streamlining PHP on OpenBSD",
4 "link": "https://anil.recoil.org/notes/php-port-layout-openbsd",
5 "updated": "2002-06-24T00:00:00",
6 "published": "2002-06-24T00:00:00",
7 "summary": "<p>I've committed a big improvement to the PHP port on OpenBSD, by switching from a complex set of FLAVOR tags over to a set of independently installing "multi packages".</p>\n<p>The first thing I did was to import the core PHP without any extensions.</p>\n<pre><code>commit 15dc0f67ef5fd0cae9fb841e608b90b9f51c71ca\nAuthor: avsm <avsm@openbsd.org>\nDate: Mon Jun 24 19:23:41 2002 +0000\n\n Import php4-core-4.2.1\n \n Installs the barebones php4 with only the gettext, iconv and recode\n modules compiled in.\n \n All of the other modules have to be installed as shared modules on\n top of this.\n \n In addition to the Apache module, this package also includes a php\n command-line binary which can be used in shell scripts. The binary\n uses the same /var/www/conf/php.ini file as the Apache module.\n \n There is some non-i386 breakage at the moment (notably macppc).\n</code></pre>\n<p>After that, I imported in the extensions system which has many more dependencies, and that generates the multi packages.</p>\n<pre><code>commit a5c226010f93bd3ce70667b801d6518354f44914\nAuthor: avsm <avsm@openbsd.org>\nDate: Mon Jun 24 19:27:46 2002 +0000\n\n Import php4-4.2.1 extensions\n \n This module generates a bunch of php4 extensions as shared modules,\n and seperates them out into multiple packages.\n \n End result is that you can pkg_add individual modules now without\n getting into the mess of flavors that we've had in the past.\n</code></pre>\n<p>This should make the use of <code>pkg_add</code> for PHP much simpler for new users. Any problems, please file a bug report or let me know.</p>",
8 "content": "<p>I've committed a big improvement to the PHP port on OpenBSD, by switching from a complex set of FLAVOR tags over to a set of independently installing "multi packages".</p>\n<p>The first thing I did was to import the core PHP without any extensions.</p>\n<pre><code>commit 15dc0f67ef5fd0cae9fb841e608b90b9f51c71ca\nAuthor: avsm <avsm@openbsd.org>\nDate: Mon Jun 24 19:23:41 2002 +0000\n\n Import php4-core-4.2.1\n \n Installs the barebones php4 with only the gettext, iconv and recode\n modules compiled in.\n \n All of the other modules have to be installed as shared modules on\n top of this.\n \n In addition to the Apache module, this package also includes a php\n command-line binary which can be used in shell scripts. The binary\n uses the same /var/www/conf/php.ini file as the Apache module.\n \n There is some non-i386 breakage at the moment (notably macppc).\n</code></pre>\n<p>After that, I imported in the extensions system which has many more dependencies, and that generates the multi packages.</p>\n<pre><code>commit a5c226010f93bd3ce70667b801d6518354f44914\nAuthor: avsm <avsm@openbsd.org>\nDate: Mon Jun 24 19:27:46 2002 +0000\n\n Import php4-4.2.1 extensions\n \n This module generates a bunch of php4 extensions as shared modules,\n and seperates them out into multiple packages.\n \n End result is that you can pkg_add individual modules now without\n getting into the mess of flavors that we've had in the past.\n</code></pre>\n<p>This should make the use of <code>pkg_add</code> for PHP much simpler for new users. Any problems, please file a bug report or let me know.</p>",
9 "content_type": "html",
10 "author": {
11 "name": "Anil Madhavapeddy",
12 "email": "anil@recoil.org",
13 "uri": "https://anil.recoil.org"
14 },
15 "categories": [],
16 "rights": "(c) 1998-2025 Anil Madhavapeddy, all rights reserved",
17 "source": "https://anil.recoil.org/news.xml",
18 "links": [],
19 "backlinks": []
20}