So I'm trying to install a software package that requires PEAR, which is some kind of extension and package manager for PHP. Well hey, I think to myself. About frickin' time someone tried to get that cross-compiling rat's nest under control.
So first I try using yum. Being on Red Hat and all.
# yum search pear Loading "installonlyn" plugin Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.main(sys.argv[1:]) File "/usr/share/yum-cli/yummain.py", line 82, in main base.getOptionsConfig(args) File "/usr/share/yum-cli/cli.py", line 147, in getOptionsConfig disabled_plugins=opts.disableplugins) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 152, in _getConfig startupconf.pluginconfpath,disabled_plugins) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 285, in doPluginSetup plugin_types, confpath, disabled_plugins) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 140, in __init__ self._importplugins(types) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 181, in _importplugins self._loadplugin(modulefile, types) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 198, in _loadplugin module = imp.load_module(modname, fp, pathname, description) File "/usr/lib/yum-plugins/rhnplugin.py", line 25, in ? import up2date_client.up2dateAuth as up2dateAuth ImportError: No module named up2date_client.up2dateAuth
Wonderful. Okay, forget about yum, since it's off in we-have-Python-religion-and-have-no-patience-for-your-heathen-error-checking land.
Instead, let's look up PEAR itself:
Ah! That sounds promising, eh? I mean, boo on you guys for assuming I have PEAR already when I'm clearly here looking for instructions on how to install it; I don't imagine you guys have ever operated on a system that wasn't built from sources and has everything imaginable already installed, but whatever: there's a handy little web-based PHP installer I should be able to use. It's got its own dedicated domain and hard-coded URL for everyone to hit, even—so surely that's something I can rely on. "go-pear". http://pear.php.net/go-pear! Well then, let's go! Go PEAR!
Uh.
God dammit I am starting to hate the Open Source community. They cleverly designed a single point of failure, and then let it fail.
Don't suppose clicking on that "Quality Assurance" link right above it will help, eh?
Oh well: let's just go download it from here.
Oh goodie, you mean the best way to install PEAR is to run the pear command? Yeah, I'll do that, you morons.
Anyway, there's a download link. Let's just grab that. And unpack the tarball. And read the README file, which is useless. And read the INSTALL file, which starts out assuming I have nothing better to do than compile the whole PHP mess from scratch all over again:
Unix ==== make sure you have enabled default extensions, and if you want faster downloads, enable the zlib extension. You must also enable the CLI SAPI with the --enable-cli extension directive. After this, simply run:
make install-pear
and PEAR will be automatically configured for you.
go-pear ======= For users who cannot perform the above steps, or who wish to obtain the latest PEAR with a slightly higher risk of failure, use go-pear. go-pear is obtained by downloading http://go-pear.org and saving it as go-pear.php. After downloading, simply run "php go-pear.php" or open it in a web browser (windows only) to download and install PEAR.
Ah! A dedicated domain! http://go-pear.org! Well then, let's just go use that! I'm sure it won't throw 404s at me.
Oh, nice. Nice.
Some pothead in Sweden is laughing at me right now, I'm sure of it.
Go PEAR yourself, Jorgi.
UPDATE: Lotta laffin' coming from up Scandinavia way.
|