1 |
The thing is, that while there's thew newest version (5.0.4) which had |
2 |
all/most of the bugs fixed since 5.0, the original 5.0 version is still |
3 |
being "tested". |
4 |
|
5 |
I think that after 5.0 was released you should have waitied for about a |
6 |
month or so to let people discover bugs like they did, and released |
7 |
patches/updates. |
8 |
5.0.4 has been stable for quite a while, meaning most of the major things |
9 |
are fixed if not all of them. |
10 |
So atleast add it to the tree, if not stable then atleast masked. |
11 |
|
12 |
On 4/25/05, Duncan <1i5t5.duncan@×××.net> wrote: |
13 |
> |
14 |
> Omer Cohen posted <30e61698050422051322736ee3@××××××××××.com>, excerpted |
15 |
> below, on Fri, 22 Apr 2005 14:13:51 +0200: |
16 |
> |
17 |
> > PHP 5.0 was released a long time ago, and alot of fixes and patches were |
18 |
> > released after it to make sure it's sable. |
19 |
> > |
20 |
> > According to PHP.net <http://PHP.net> <http://php.net/> the stable |
21 |
> versions are PHP 5.0.4 && |
22 |
> > 4.3.11 |
23 |
> > 4.3.11 is marked stable, but 5.0.4 dosn't even exist on the tree. |
24 |
> > |
25 |
> > 5.0.0 isn't marked at all, and everything till 5.0.3-r2 is marked are |
26 |
> hard |
27 |
> > masked and still being tested. |
28 |
> > |
29 |
> > It's been like this for a long time now. |
30 |
> > |
31 |
> > As a PHP developer I believe that 5.0.4 is more then stable, and should |
32 |
> be |
33 |
> > added and marked stable. |
34 |
> > |
35 |
> > I don't wanna override the system and install it manualy. |
36 |
> |
37 |
> OK, I see a big discussion, but nobody has yet made this point, directly |
38 |
> at least, so here it is... |
39 |
> |
40 |
> I agree that 5.0.4 should at least be in the tree, if upstream is calling |
41 |
> it stable. |
42 |
> |
43 |
> The point that should be emphasized, however, is that there's a /big/ |
44 |
> difference between the upstream application being "stable", and Gentoo's |
45 |
> particular instance, that is, the ebuild script that merges it onto a |
46 |
> Gentoo system, being stable. Gentoo's keywording, while somewhat |
47 |
> correlating with upstream in that what upstream has declared a beta or RC |
48 |
> is often never arch-stable keyworded on Gentoo, generally serves to |
49 |
> indicate the Gentoo ebuild maintainer's evaluation of the stability of the |
50 |
> EBUILD, *NOT* the stability (or lack thereof) of the upstream source. |
51 |
> |
52 |
> Thus, as I said above, yes, the version that upstream calls "stable" |
53 |
> should reasonably be expected to be in the portage tree in some form |
54 |
> within a reasonable (few week, often less) time, however, one can't always |
55 |
> expect that said portage tree version will be marked stable just because |
56 |
> upstream defines that particular version of their product as stable, |
57 |
> because the status of the Gentoo instance of it, the ebuild, may itself |
58 |
> not be stable, on one or more archs, possibly on all of them. |
59 |
> |
60 |
> In this instance, >=php-5.0 on Gentoo is hard masked, not because of what |
61 |
> upsteam says, but because (presumably) there have been and remain |
62 |
> unresolved issues with the Gentoo deployment. Something in Gentoo's |
63 |
> previous deployments conflicts with the current 5.0 layout, and a smooth |
64 |
> transition hasn't yet been worked out and fully tested, so the 5.x series |
65 |
> remains hard masked. |
66 |
> |
67 |
> Ignoring for the moment the issue of the 5.0.4 upstream-stable version |
68 |
> itself not being in the tree at all, if a sysadmin is suitably comfortable |
69 |
> with php-5.x, and either understands the issues keeping it masked on |
70 |
> Gentoo and knows they don't apply in his case or at least is willing to |
71 |
> extend the effort to work around any issues that may appear, said sysadmin |
72 |
> is entirely free to package.unmask, or add keywords in an overlay, as |
73 |
> appropriate. That's why the portage system has been designed with that |
74 |
> flexibility in place, after all -- so it can be used at the decision of |
75 |
> the individual Gentoo user -- aka the local Gentoo system sysadmin. |
76 |
> |
77 |
> -- |
78 |
> Duncan - List replies preferred. No HTML msgs. |
79 |
> "Every nonfree program has a lord, a master -- |
80 |
> and if you use the program, he is your master." Richard Stallman in |
81 |
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
82 |
> |
83 |
> |
84 |
> -- |
85 |
> gentoo-dev@g.o mailing list |
86 |
> |
87 |
> |
88 |
|
89 |
|
90 |
-- |
91 |
Thanks, |
92 |
Omer Cohen |
93 |
www.omerc.net <http://www.omerc.net> |
94 |
omerc.net@×××××.com |