Warren Togami wrote :
[... php-eaccelerator package ...]
Sounds OK, but perhaps we should have the other guy become involved with
maintenance of that package in Extras? Maybe work with him in future
maintenance?
"The other guy"? If you're talking about the person who reported the change
and asked to get php-eaccelerator packaged, well, he also contacted me in
private asking if I'd consider packaging it on freshrpms.net too. His spec
file is based on my php-mmcache one, with very recent SuSE-compatibility
defacing he accepted from someone else, that we most certainly don't want.
I think he became the "rpm packager" for their project "by default" more
than anything else (not that I mean anything negative by that, and it's
just my impression).
I am a bit concerned about the burden of the large number
of packages under your sole maintainership. =)
...but that's not counting all of those packages that I'd like to reclaim
maintainership of! ;-)
Would php-mmcache be Obsoleted and removed then?
Why not. But there is no reason to kick it out immediately, but surely in
the not-so-distant future since mmcache isn't PHP5 compatible, whereas
eaccelerator is.