Re: Installer(s) do(es) not work
| From: | Stig S. Bakken | Date: | Mon, 18 Mar 2002 21:13:51 +0000 |
| Subject: | Re: Installer(s) do(es) not work | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5028@lists.php.net to get a copy of this message | ||
On Mon, 2002-03-18 at 13:59, Jean-Michel POURE wrote:
> Dear all,
>
> Php 4.1 binary + Apache 1.31 are installed on a Linux station.
>
> 1) According to http://pear.php.net, I downloaded /php4/pear
> and tried
> $ make scripts/pear scripts/pear-get
> $ make install-programs bin_SCRIPTS='pear pear-get'
> This does not work.
>
> 2) install-pear.txt
> I tried make install-su. It does not work.
> Shall I "loudly" complain? Saying for example your guys are trying to
> re-create the wheel (RPM or DEB already exist, why not use them?).
If we chose RPM, what should Debian users do? Install RPM in addition
to APT/DPKG? And ditto for RedHat users, should they install DPKG?
I have considered both RPM and DPKG, but PEAR's package system has some
specific requirements that I found hard to fulfill with other package
systems, without integrating deeply with the OS distribution's existing
package system (at least in Linux lingo):
* portability: the very same "100% Pure PHP" package will install on
Unix, Windows or anything PHP/PEAR runs on
* PHP extension dependencies: this would require integration with
existing package manager
* SAPI backend dependencies: ditto
And so on.
Instead, PEAR's package manager has (well, had, I haven't re-introduced
this feature to the new version yet) a some options that package
managers can use to wrap PEAR packages inside for example RPMs, and make
sure both package systems' registries are maintained.
> What will the situation be like when Php5 comes along?
PEAR will exploit new PHP 5 features, using namespaces and exceptions.
Maintainers will either declare at one point that they continue
developing their package for PHP 5 only, that they will keep developing
it for PHP 4 or that they intend to maintain both PHP 4 and PHP 5
versions.
The package manager will either use dependencies information that we
make easily available from the online database, or we define new release
states with "5" appended for use by PHP 5 releases (ex. "stable5").
> How will you manage dependencies?
Check out http://cvs.php.net//pearweb/rfc/003-dependencies.txt
- Stig