PHP PEAR Questions and Answers - Re: [PEAR-QA] Re: [QA Team] Net_URL 2.0.0 release removed

Author

Re: [PEAR-QA] Re: [QA Team] Net_URL 2.0.0 release removed - Please fix and resubmit

Cipriano Groenendal

2004-06-29, 8:56 am

> Richard expressed his refusal to rename the class on IRC. Cox agreed
> with him, saying that he didn't have to rename it. So he added the php5
> requirement and re-uploaded, so it should not install if an incompatible
> version of php is used. The API has remained the same. The only
> difference is that it is now rewritten for php5 strict.
So what would happen with a PHP4 install without Net_URL?

[root@server root]# pear install Net_URL
downloading Net_URL-2.0.0.tgz ...
....done: 5,173 bytes
requiers PHP version >= 5.0.0
Net_URL: Dependencies failed

Result: No installed version of Net_URL. Unless the user knows about the
previous version, he'd be unable to installed the entire package, eventhough
there's an older version that will install.
The 2.0.0 release should be pulled, like Lukas(?) did again just now, and it
should be released as a Net_URL2

Cipri

Daniel Convissor

2004-06-29, 4:00 pm

Hi:

On Tue, Jun 29, 2004 at 12:11:45PM +0200, Lukas Smith wrote:
> Cipriano Groenendal wrote:
> [additional citation is probably missing --dc]
>

How OLD is Richard? Between this, and is obnoxious treatment of me when I
mentioned his inadvertent use of a CRLF in Net_URL.php (let alone that
file now being all CRLF), he acts like he's either very old or very young.

[color=darkred]

Similarly, if one has two version of PHP installed though one PEAR path,
like I do, one could install it under PHP 5, then switch to PHP 4 and be
screwed. Not fun.

[color=darkred]
> Anyone who has php4 and php5 installed will probably have separate pear
> paths. Or should have.

Sounds like an unncecessary waste of time and space.

> So for the special case that the php5 version is api compatible with the
> php4 version I can see that we may get around the new major version
> requirement.

I hope not.

> But for this reason it needs to be handled differently than
> a new major version. Instead it should be the same major version in
> multiple variations for specific php releases.

So, what happens when just the PHP 4 or PHP 5 version needs a bugfix and
release? How are the files going to be distinguished? Sounds like a pit
of quicksand.

At this point in time (with PHP 4 in wide use) using a new major version
will really clarify things. Perhaps a year or two from now when PHP 5
has major penetration, the point will be less important.

--Dan

--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409

Sponsored Links