ID:               23714
 Updated by:       [EMAIL PROTECTED]
 Reported By:      ch at bumerang dot ro
-Status:           Open
+Status:           Assigned
 Bug Type:         Documentation problem
 Operating System: HPUX
 PHP Version:      Irrelevant
-Assigned To:      
+Assigned To:      philip
 New Comment:

It would be great, please provide a nice summary and we'll link to the
full tutorial. Are you still interested in doing this? A plain text
file would be fine too, I'll convert it into DocBook form.


Previous Comments:
------------------------------------------------------------------------

[2006-02-24 14:04:10] [EMAIL PROTECTED]

Patch, diffed against the current xml-file are very welcome.
Generic, uptodate, install instructions for HP UX is valuable for the
manual.
Thanks
Friedhelm

------------------------------------------------------------------------

[2006-02-22 23:02:43] flconseil at yahoo dot fr

Yes, The HPWS package from HP is a solution, but I wanted to compile
the package by myself because I have several Unix flavors to manage and
I want them to have the same software versions, and to be able to
regenerate it when I want, instead of waiting for HP.

Another reason is that I have tried to get some help from HP, in order
to know how they compile their package, and it has proved to be
absolutely impossible to get any information. I don't like this kind of
behavior. As I discovered later when doing it by myself, because of
problems related to the HP-UX OS itself, they practically force most
users to depend on their package. It is not my view of Open SOurce
philosophy. As most of these big companies, they like to take, but not
to give...

So, I sent several days compiling a full Apache 2.0 + PHP 5.1.2
package, including every libraries they depend on. This package also
includes most Apache modules and PHP extensions (zlib, SSL, LDAP,
iconv, expat, xml, xslt, gd, png, Xpm, jpeg, freetype, bzip2, curl,
MySQL, PostgreSQL, Oracle, AdoDB).

I have also written a complete howto document, describing how to build
everything from scratch, from the place to get the source packages, to
the way to check that everything works OK. This document is available
at :

http://flaupretre.free.fr/redir.php?key=build_apa_hpux

I am ready to write a 1 or 2 page resume of the document for the PHP
documentation page (the full document is about 13 page long), with a
link to the full document, for instance.

Tell me what you think about it.

------------------------------------------------------------------------

[2005-05-07 05:00:02] [EMAIL PROTECTED]

I believe the "best" method for installing PHP (and Apache) is to go
here:

http://www.software.hp.com/

And install one of the found packages. Searching for PHP yields several
packages, for example:

HP-UX Apache-based Web Server v.2.11 powered by Apache, Tomcat, Webmin

We should most likely remove all current documentation and simply
mention how to install one of these packages. Well, at least until
someone who knows HP-UX can add additional information.

------------------------------------------------------------------------

[2005-04-26 17:41:22] [EMAIL PROTECTED]

wk at mailstation dot de, can you please write some notes for current
version or at least point us to sources you used? Everlasting honor
will be yours :-).

------------------------------------------------------------------------

[2004-10-20 13:39:06] wk at mailstation dot de

I have installed PHP 4.x and 5.x on HP-UX 10.xx and 11.xx.

a) The documentation *is* outdated and even wrong (e. g., you *can*
build PHP as a shared module on HP-UX). The reference to an unspecified
"Apache page" is misleading even.

b) No, take it out completely. Having nothing about HP-UX is better
than that stuff.

c) is therefor irrelevant.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/23714

-- 
Edit this bug report at http://bugs.php.net/?id=23714&edit=1

Reply via email to