Re: [ANNOUNCEMENT] PEAR-1.3b1 (beta) Released.

Hi Klaus, These features are useful - but only possible if the PEAR core starts using error codes, as otherwise there is no way to determine what the error message returned from downloading means. I have just written a fix for the preferred_state bug that uses an error code, and the rest of the core will have to migrate to this usage before anything as smart as your example can happen :) Greg Klaus Guenther wrote:

Pierre-Alain Joye wrote:

# pear upgrade file_passwd-alpha File http://pear.php.net:80/get/file_passwd-alpha not valid (received: HTTP/1.1 404 Not Found)

The message is not helpful but correct. There is no alpha release for File_passwd, a 404 without nice message sounds like a brutal message but a correct one ;)

lol true, but... it's most unhelpful. /get/package-state should be handled by a script that is smart enough to understand that if you enter "pear install package-alpha" you don't want to install version 0.1.0 when version 2.0 stable is out, simply because 0.1.0 is the latest. Personally, I'd like to see something like this: ........... # pear install Foo-alpha Warning: latest alpha release is depreciated. Latest versions by state: snapshot: devel:

alpha:   0.1.0    2001-08-01
beta:    2.0rc2    2003-09-10
stable:    2.0    2003-09-20

Use --force to install anyway. # ........... Of course, this is by the current versioning scheme, not according to the new RFC for versioning, but this can easily be adapted. ........... # pear install Foo-snapshot Error: no snapshot release found. Latest versions by state: snapshot: devel:

alpha:   0.1.0    2001-08-01
beta:    2.0rc2    2003-09-10
stable:    2.0    2003-09-20

Latest version: 2.0 stable. # pear install Foo ........... Or maybe simply the last 3 releases could be shown (with version, release date and state). That would be helpful, too. The point is, we need some information, the new features are not as userfriendly as the old ones. Perhaps the reasoning is that people won't use them that much anyway. I know I'll use them, and I'd not like to have to look up the package page when I'm working on SSH. Not saying that you can't view the pear site on lynx, it's just that it's... too much effort :-P And I've never used the pear info command much because it's more effort that I'd like to expend on a regular basis. I'd also like to be able to set a flag so I can see the changelog automatically when I upgrade. It shouldn't be difficult to implement, and would be a useful replacment for those useless empty "w" messages that used to appear for each upgrade. Klaus