Re: PEAR installer and the PHP dep
| From: | Helgi Þormar Þorbjörnsson | Date: | Mon, 28 Jul 2008 16:28:23 +0000 |
| Subject: | Re: PEAR installer and the PHP dep | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50476@lists.php.net to get a copy of this message | ||
On Mon, Jul 28, 2008 at 4:18 PM, Brett Bieber <brett.bieber@gmail.com> wrote:
> Eh, this would be one I would classify as, not good enough. It's the
> "a lot of issues" part that I think should be documented. -- not
> official documentation per-se, but aired out in public somewhere.
>
>> for 4.3 -> 4.4 I have no simple answer since it's one of those just
>> because, PEAR runs fine on 4.3 but not actively tested on it but we do
>> need to nudge users forward and well memory corruption issues ... 4.4
>> fixed that ;) hehe
>
> Hmm, now I'm thinking of Yahoo's graded browser support page ---
>
> http://developer.yahoo.com/yui/articles/gbs/index.html
>
> A = 5.2, 4.4 etc etc. Known working - fully supported.
> B = 5.1
> X = 5.0, 4.3, 6.0 unknown/unexpected, don't expect us to respond to
> any bug reports on these versions
>
> That way we could say --- we know it works, and we fully support
> versions Foo, Bar, Baz, but if you're using Fit, Bit, Ban, you're on
> your own.
I must say - Why ? That's still mean I'd have to keep the min
requirement at 4.3 and allow 5.0 installations ... which is what I was
hoping we could get rid of somehow - Most, if not all projects I know
of out there have 4.4 and 5.1+ deps claiming exactly what I've been
saying, at least I can't see why we should add some funny table with
some "works, doesn't work" into our manual since well ... I think our
manual is not structured well enough for users to find this kind of
information easily.
Makes me tho wonder a bit why this dep bump would need such docs and
not our 4.2 -> 4.3 move, don't misunderstand me tho - I do see where
you are coming from with this, we should be open to our developers and
end users on issues like this.
How about this compromise, we add 4.3.11 as min dep (latest 4.3
release) and we throw in a recommend 5.2 ... Not sure what I'd want to
do with 5.0, ideally I'd want to disallow all 5.0 except for the
latest one - so we keep with the 4.3 schema ... we can observe the
uptake of the newest PEAR release and how that reflects on the PHP
versions being used, if people are actually upgrading or not, does
that sound like a more acceptable solution for this PEAR release and
perhaps the 4.4 and 5.0 exclusion for 1.9 ?
Just another idea tho with my first one ...
Regards
Helgi