EXT: pear¶

Table of Contents¶

EXT: pear 1

Introduction 1

What does it do? 1

Screenshots 2

Users manual 2

FAQ – How to translate the Installer 2

FAQ – How to get beta or alpha packages 2

Adminstration 2

Always secure the PEAR Manager after you have used it3

HowTo switch off the “auto-pilot” for include_path 3

Special for Windows 3

Configuration not needed 3

Tutorial to use PEAR-packages 3

Known problems 4

To-Do list 4

Changelog is pear/ChangeLog 4

Introduction¶

$TYPO3_CONF_VARS['PEAR']['isAuto']
#and
$TYPO3_CONF_VARS['PEAR']['packagePath']

Users manual¶

For Admins: just install the extension, then follow the Administration-part. From time to time check for updates of the packages. In future the updates will also be handled by the Extension Manager.

For Extension-Developers: Use the “ini_set”-version for include_path, because so users of your extension do NOT have to care for that setting. Each PEAR-package has a version-function - just test that! In future the kickstarter will have the dependency-setting “pear-depends” - so you can set what package-versions you need.

Adminstration¶

Just klick at "download", then "install", "next".

Configuration while install: You need not to change something! Just if you're behind a proxy you have to insert the name.

Now you see the install-process of the most important PEAR-packages.

When it's ready you see the link at the footer of the page:"Start Web Frontend of the PEAR Installer >>"

As test type this in the search-box:"PEAR_Info"

Configuration not needed¶

The installation goes automatically!! You need not to change something! Just if you're behind a proxy you have to insert the name.

Tutorial to use PEAR-packages¶

When your installation is ready the PEAR Manager shows you how to set the include_path to localconf/ext/pear/PEAR .

As a start: install the package “PEAR_Info” (just type the name in the search-box of PEAR Manager), check that include_path is correct, disable the PEAR Manger again, and then put this into a new extension or as single PHP-file:

<?php
    require_once 'PEAR/Info.php';

    // If you need to set a http_proxy value at run-time you can use the
    following, this must be called BEFORE instantiating the PEAR_Info object
    // PEAR_Info::setProxy('your.proxy.here');

    // Instantiate PEAR_Info object
    $info = new PEAR_Info();

    // Show output
    $info->show();
?>

Known problems¶

The Safe Mode/ open_basedir – restriction is not handled in the moment. If you find a solution then please contact me at info@patchworking.de , Daniel Bruessler. If somebody is behind a proxy then please tell me what settings are needed. Thanks!!

For Windows-problems see GNU Utils (http://gnuwin32.sourceforge.net/packages/wget.htm)

If you find a bugs so please report it to http://bugs.typo3.org bugtracker category “tx_pear”.

To-Do list¶

Workaround for current and old versions of Extension Manager:

• ship the PEAR-class with your extension - as fallback
• link from your BE-module to the PearManager (if installed) so that people can update by itself

Next step for this Extension:

create "bridge"-functions or a service that uses this pear-extension to get the right package-version

Future version of Extension Manager: Call pear-extension to check if package X ist available and what version it has, make request for installation when package X is in need. Provide settings for stable / beta/ alpha in Extension Manager. Put PEAR Manager as function into the Extension Manager.

When Extension Manager and TER provides pear-dependencies the kickstarter can be extended to use the kind "pear-depends".

Changelog is pear/ChangeLog¶

EXT: pear - 4