PHP Wiki - pear:pear2:pyrus

backport_to_pear

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 13:46	current
Line 1:	Line 1:
	+	PEAR2 backported to PEAR(1)

	+	Two major changes -
	+	- supporting the 'paranoia' option in PEAR. - [[pear:rfc:pear2_versioning_standard_revision]]
	+	- allowing packages using pear2 standards to be released on pear.php.net
	+
	+	Through the use of the 'paranoia' option in Pyrus which prevents BC breaking changes to be upgraded, packages in PEAR1 could have BC breaking changes without affecting existing installations, as long as they require pyrus as the pearinstaller (IE: minimum pearinstaller=2.0.0a1)
	+
	+	This means we could modify the PEAR2 standards, and make them work for the existing PEAR packages, and allow them to be upgraded at will.
	+
	+	=== Pros: ===
	+	* Keeps pear.php.net running
	+	* New code behind the website
	+	* No confusion over PEAR and PEAR2, people won't see it as abandoning the current code base
	+
	+	=== Cons: ===
	+
	+	* Potential name conflicts
	+
	+	=== Changes Required: ===
	+
	+	* Change namespace to PEAR\ within the PEAR2 standards code
	+	* Documentation has to be able to reflect v1 and v2 properly if they are wildly different (PHP 4 code vs. PHP 5.3+ code with other standards)

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/06/25 22:36		current
Line 185:		Line 185:
	* The ability to freeze / hold a package, while frozen, one can not upgrade it (potentially not remove it either).http://pear.php.net/bugs/10570		* The ability to freeze / hold a package, while frozen, one can not upgrade it (potentially not remove it either).http://pear.php.net/bugs/10570
	* Ability to migrate one package from X channel to Y (PHPUnit) http://pear.php.net/bugs/4208 this one does impose some security implication we have to solve		* Ability to migrate one package from X channel to Y (PHPUnit) http://pear.php.net/bugs/4208 this one does impose some security implication we have to solve
		+	* [Greg Note: ^^ This is already implemented]
	* Look at AMO, yum, apt-get, canory and friends (PackageKit ?)		* Look at AMO, yum, apt-get, canory and friends (PackageKit ?)
	* rpm / deb generations out of the box (external packages like now ?) - potentially others, as plugins perhaps to have less pollution		* rpm / deb generations out of the box (external packages like now ?) - potentially others, as plugins perhaps to have less pollution

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 13:46	current
Line 1:	Line 1:
	+	A potential sitemap for pyrus.php.net

	+	* Home
	+	* Downloads & Changelog
	+	* About/Documentation
	+	* Support
	+	* Developers/Development
	+	* Plugins
	+	* Generator (the bundle generator effectively)
	+