Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: master
Commits on Oct 16, 2011
  1. @fabpot
Commits on Oct 8, 2011
  1. @fabpot

    prepared 1.0.4 release

    fabpot authored
  2. @fabpot

    added CHANGELOG

    fabpot authored
  3. @fabpot

    fixed CS

    fabpot authored
  4. @fabpot

    merged branch ocubom/dependency-groups (PR #31)

    fabpot authored
    Commits
    -------
    
    2614d52 added optional dependency groups in index file
    7991f36 added support for PEAR Optional Dependency Groups
    
    Discussion
    ----------
    
    PEAR Optional Dependency Groups
    
    Pirum does not support PEAR Optional Dependency Groups. When you try to install this kind of packages from a Pirum served channel, the PEAR installer fails to detect the group and aborts with an error. The patch generates the correct structure so the channels served by Pirum can hold dependency groups without problems.
    
    PEAR allows an "optional dependency groups" that define blocks of optional packages. Each group provides some feature (usually "plugins" or drivers) and must be installed in a block.
    
    This dependencies are almost indentical to normal dependencies but enclosed with <group> tags that defines the group name and provides a description ('hint'):
    
    ```xml
    <group name="remoteshell" hint="Add support for Remote Shell Operations">
    	<package>
    		<name>SSH_RemoteShell</name>
    		<channel>pear.php.net</channel>
    	</package>
    	<extension>
    		<name>ssh2</name>
    	</extension>
    </group>
    ```
    
    PEAR needs a "special format" in package deps.[version].txt file to hold this dependencies: The dependency array to be serialized must looks like (reverse engineering from http://pear.php.net/rest/r/mdb2/deps.2.5.0b3.txt, seems to be undocumented):
    
    ```PHP
    <?php
    array(
    	'required' => array(...),
    	'group' => array(
    		array(
    			'attribs' => array('hint' => '...', 'name' => 'grp1'),
    			'package' => array('name' => 'dep1', 'channel' => '...', ...),
    		),
    		array(
    			'attribs' => array('hint' => '...', 'name' => 'grp1'),
    			'package' => array('name' => 'dep2', 'channel' => '...', ...),
    		),
    		array(
    			'attribs' => array('hint' => '...', 'name' => 'grp2'),
    			'package' => array('name' => 'dep3', 'channel' => '...', ...),
    		),
    	),
    )
    ```
    
    Each entry is a package, subpackage or extension that belongs to one group. The attribs key indicates the group the package belongs to and the dependency is defined as usual. If one package belongs to several groups or the group has more than one package, must to be duplicated.
    
    The patch generates this array so the channels served by pirum holds dependency groups without problems.
Commits on Sep 29, 2011
  1. @fabpot

    adde composer.json

    fabpot authored
Commits on Sep 26, 2011
  1. @fabpot
Commits on Sep 19, 2011
  1. @ocubom

    added optional dependency groups in index file

    ocubom authored
    Shows how to install Optional Dependency Groups defined for each package in main index file.
  2. @ocubom

    added support for PEAR Optional Dependency Groups

    ocubom authored
    Change the generation of deps.txt file when a package uses Optional Dependency Groups (http://pear.php.net/manual/en/guide.developers.package2.dependencies.php).
Commits on Sep 16, 2011
  1. @fabpot

    simplified code (thanks @yunosh)

    fabpot authored
Commits on Sep 15, 2011
  1. @fabpot

    added support for channel mirrors

    fabpot authored
    <?xml version="1.0" encoding="UTF-8" ?>
    <server>
      <name>pear.pirum-project.org</name>
      <summary>Pirum PEAR channel</summary>
      <alias>pirum</alias>
      <url>http://pear.pirum-project.org</url>
      <mirror>http://fr.pear.pp.org</mirror>
      <mirror>https://secure.pear.pp.org</mirror>
    </server>
  2. @fabpot
  3. @fabpot

    fixed CS

    fabpot authored
  4. @fabpot

    fixed CS

    fabpot authored
  5. @fabpot

    prepared 1.0.3 release

    fabpot authored
  6. @fabpot

    merged branch janl/master (PR #22)

    fabpot authored
    Commits
    -------
    
    6217b26 allow versions like 0.0.1a or 0.0.2b1
    
    Discussion
    ----------
    
    Allow version numbers like 0.0.1a or 0.0.2b1
    
    Some pear packages in the wild (ext/memcached e.g.) will use the above package naming and `pear package` will happily create a filename like foo-0.0.2b1 which Pirum then will refuse to process.
    
    The patch updates the package name validation regex to allow the characters "a" and "b" next to the "alpha", "beta" etc. labels.
    
    ---------------------------------------------------------------------------
    
    by beberlei at 2011/06/01 06:12:21 -0700
    
    I think version_compare() or PEAR might not allow this, not sure though.
    
    ---------------------------------------------------------------------------
    
    by janl at 2011/06/01 06:52:39 -0700
    
    Then `pear package` should not produce such a package and reject it from there :)
    
    I don't necessarily care where the fix is applied, but the inconsistency poses a problem for me.
    
    EDIT: `version_compare()` works as expected:
    
    > php -r 'var_dump(version_compare("0.0.1", "0.0.1a1"));'
    > int(1)
    
    ---------------------------------------------------------------------------
    
    by till at 2011/06/01 15:52:02 -0700
    
    Talked to Brett (Bieber) on IRC, he mentioned to look into `PEAR/PackageFile/v2/Validator.php`:
    
        /^\d+(?:\.\d+)*(?:[a-zA-Z]+\d*)?\\z/
    
    That's apparently the regex used to validate the _version_.
  7. @fabpot
  8. @fabpot

    tweaked default style

    fabpot authored
  9. @fabpot
Commits on Sep 1, 2011
  1. @fabpot

    updated domain name

    fabpot authored
Commits on Aug 26, 2011
  1. @fabpot

    merged branch superhaggis/master (PR #29)

    fabpot authored
    Commits
    -------
    
    4ea35e4 Edited README grammar and standardised message formatting.
    
    Discussion
    ----------
    
    Grammatical tweaks
    
    Please note: you will need to update the screenshots in your online documentation to reflect the changes in this PR.
  2. @superhaggis
Commits on Jul 25, 2011
  1. @fabpot
  2. @fabpot

    prepared 1.0.2 release

    fabpot authored
  3. @fabpot

    fixed Atom feed (closes #21)

    fabpot authored
Commits on Jun 22, 2011
  1. @fabpot

    moved the creation of .tar when building the PEAR channel (this allow…

    fabpot authored
    …s to put the .tgz in get/ and run build without running add)
Commits on Jun 18, 2011
  1. @fabpot

    merged branch kukulich/patch-1 (PR #24)

    fabpot authored
    Commits
    -------
    
    9ad012a Added pirum.bat for Windows
    
    Discussion
    ----------
    
    Pirum.bat for Windows
  2. @fabpot

    merged branch lyrixx/patch-1 (PR #23)

    fabpot authored
    Commits
    -------
    
    3e4ad18 Fixed doc
    
    Discussion
    ----------
    
    Fixed doc
  3. @kukulich

    Added pirum.bat for Windows

    kukulich authored
Commits on Jun 3, 2011
  1. @lyrixx

    Fixed doc

    lyrixx authored
Commits on Jun 1, 2011
  1. @janl
Commits on Mar 27, 2011
  1. @fabpot

    prepared 1.0.1 release

    fabpot authored
  2. @yunosh @fabpot

    Add support for <validatepackage> tags in channel.xml.

    yunosh authored fabpot committed
    Still needs to be documented. New tags for pirum.xml are
    <validatepackage> and <validateversion>
  3. @yunosh @fabpot

    Fix cleanup of temporary directories.

    yunosh authored fabpot committed
Commits on Mar 1, 2011
  1. @manuelpichler

    Add support for valid snapshot stability

    manuelpichler authored
    This commit adds support for the valid PEAR package stability "snapshot"
    as documented in PEAR manual[1].
    
    [1] http://pear.php.net/manual/en/guide.developers.package2.stability.php
Something went wrong with that request. Please try again.