Request for features in PEAR 2.0 (codename Pyrus)

Hi,

As some of you know, plans are well underway for the next generation
PEAR installer, which will be named Pyrus barring any problems with
trademarks or other naming issues. Pyrus is the genus of the pear
fruit. The goal is to encompass even more functionality than the
current PEAR installer.

The roadmap for PEAR 2.0 is at
http://pear.php.net/bugs/roadmap.php?package=PEAR

Please peruse the feature list and if you have ideas for new features,
open a feature request at http://pear.php.net/bugs/report.php?package=PEAR

The current source for the new installer is in CVS at pear-core/PEAR2.

Thank you,
Greg

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1.) I'd like to see -c (channel) added to all calls so I don't need
to muck around with my default_channel for various operations.
(namely authentication)

2.) I'd like to be able to push packages directly from the command
line. ie. pear release -c pear.php.net Foo-1.0.0.tgz.

3.) RunTests should be factoried out so we can integrate multiple
testing frameworks more quickly into PEAR.

4.) pear send-beer -c pear.php.net -u jstump should work
appropriately ... ideally I'd be able to define preferred beers and
it'd randomly send me one of my favorites. The user calling the
function would, of course, have to authenticate their paypal
information.

- --Joe

On May 22, 2007, at 9:20 AM, Greg Beaver wrote:

> Hi,
>
> As some of you know, plans are well underway for the next generation
> PEAR installer, which will be named Pyrus barring any problems with
> trademarks or other naming issues. Pyrus is the genus of the pear
> fruit. The goal is to encompass even more functionality than the
> current PEAR installer.
>
> The roadmap for PEAR 2.0 is at
> http://pear.php.net/bugs/roadmap.php?package=PEAR
>
> Please peruse the feature list and if you have ideas for new features,
> open a feature request at http://pear.php.net/bugs/report.php?
> package=PEAR
>
> The current source for the new installer is in CVS at pear-core/PEAR2.
>
> Thank you,
> Greg
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGUx9Oh0MUGpYY9OQRAlcQAJ46P/glMBykV3iwvCHOXSsOalEWJQCfW+Mp
froyJChyEBEcb1sD6WxLXls=
=tRtz
-----END PGP SIGNATURE-----

On 5/22/07, Joe Stump <joe@joestump.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1


3.) RunTests should be factoried out so we can integrate multiple
> testing frameworks more quickly into PEAR.


Don't most of those testing frameworks have something like phpunit ?
AllTests.php iirc ?
Atm we do support phpt phpunit (if AllTests.php is available) and outputting
in TAP
So wont this "integration" just be about locating the all tests file of the
given framework and running that ?

- Helgi

Greg Beaver wrote:
> Hi,
>
> As some of you know, plans are well underway for the next generation
> PEAR installer, which will be named Pyrus barring any problems with
> trademarks or other naming issues. Pyrus is the genus of the pear
> fruit. The goal is to encompass even more functionality than the
> current PEAR installer.
>
> The roadmap for PEAR 2.0 is at
> http://pear.php.net/bugs/roadmap.php?package=PEAR
>
> Please peruse the feature list and if you have ideas for new features,
> open a feature request at http://pear.php.net/bugs/report.php?package=PEAR
>
> The current source for the new installer is in CVS at pear-core/PEAR2.
>
> Thank you,
> Greg
>
>
The ability to easily make relative tarball of a package (with its
dependencies) that can be deployed just by extracting (ie all
replacements already done)

-josh

Greetings,

Attempted to submit a feature request at
http://pear.php.net/bugs/report.php?package=PEAR and was greeted with the
"Critical internal error: could not send email to your address" message,
though http://pear.php.net/account-request.php indicates that I should be
able to report a feature request/bug & create an account as needed. Where's
the logic hole on my part?

In any case, here's the body of the request:

" An additional interface to 'pear install' or 'pear upgrade' to include,
via RSS or otherwise, a currently buglist would be beneficial; betraying my
Debianphilia, something along the lines of apt-listbugs would be extremely
beneficial when it comes to deployment.

Cheers."


-Ryan



> On May 22, 2007, at 9:20 AM, Greg Beaver wrote:
>
> Hi,
>
> As some of you know, plans are well underway for the next generation
> PEAR installer, which will be named Pyrus barring any problems with
> trademarks or other naming issues. Pyrus is the genus of the pear
> fruit. The goal is to encompass even more functionality than the
> current PEAR installer.
>
> The roadmap for PEAR 2.0 is at
> http://pear.php.net/bugs/roadmap.php?package=PEAR
>
> Please peruse the feature list and if you have ideas for new features,
> open a feature request at http://pear.php.net/bugs/report.php?
> package=PEAR
>
> The current source for the new installer is in CVS at pear-core/PEAR2.
>
> Thank you,
> Greg
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg Beaver wrote:
> Hi,
>
> As some of you know, plans are well underway for the next generation
> PEAR installer, which will be named Pyrus barring any problems with
> trademarks or other naming issues. Pyrus is the genus of the pear
> fruit. The goal is to encompass even more functionality than the
> current PEAR installer.
>
> The roadmap for PEAR 2.0 is at
> http://pear.php.net/bugs/roadmap.php?package=PEAR
>
> Please peruse the feature list and if you have ideas for new features,
> open a feature request at http://pear.php.net/bugs/report.php?package=PEAR
>
> The current source for the new installer is in CVS at pear-core/PEAR2.
>
> Thank you,
> Greg

Would be great to make my repository relocatable. I just ran through
this and was faster re-installing 25 packages than looking through the
registry and change paths...

Bye, Stephan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGU1NA8qQ9XV7tBNQRArKYAKDNEf23QuM6rOiQdUTSOo wxS2MljgCePzJ7
8Ylu9xAfFspOoW4YObvugNM=
=SP2s
-----END PGP SIGNATURE-----