[csw-maintainers] gar and php question

Philip Brown phil at bolthole.com
Mon Jun 6 20:20:02 CEST 2011


On Mon, Jun 6, 2011 at 10:53 AM, Ben Walton <bwalton at opencsw.org> wrote:
> Excerpts from Philip Brown's message of Mon Jun 06 13:09:57 -0400 2011:
>
>> > Well, it is useful as php4 is not supported upstream and we have
>> > the supported branch (although even our php5 version is
>> > unsupported now until I get the update finished).  Removing it
>> > from the catalog won't prevent those that want it from getting it,
>> > but we should make those people 'work' for it
>>
>> why?
>
> Because they can file bugs on it or expect some level of response from
> us because it's in the catalog.

again, this is no different from our many other packages that are
orphaned, and people will get no response from doing that on those
either :-/

>> we have plenty of packages that are no longer "supported" (ie:
>> orphaned), but we still keep available.  What specific problem does
>> it solve to remove php4 from our catalog?
>
> It's legacy software (as deemed by the upstream).  What benefit is
> there in retaining it?

okay, that's a better reason to consider removing it.
But that being said.. we ARE sometimes in the "business" of providing
"legacy" frameworks.


Doing a bit of digging, it appears we agreed on the following, back in 2009:

>> it doesnt look like there are any dependancies of OURS that use it.
>> However, it would need to be carefully announced ahead of time to users.
>
>Agreed.
>
>-Ben

So, please go ahead and announce , that we plan to remove it within
[insert timeframe here].
(and to holler if this for some reason is a problem for someone, and why)

And then after that time, we can remove it.
Since this is by definition extreme legacy software, the people may
not keep up to date with announcements, etc :-} so we may want to set
a somewhat longer timeframe than would otherwise be fine.

July 1st?


More information about the maintainers mailing list