[irony]oh well, you just have to give it to the gentoo community,
they're always polite and glad to help.[/irony]
thanks for the tip about the local overlay, i have to admit i didn't
think about that right away. the local overlay seems indeed to be the
easiest solution.
sorry about the question, but i wasn't complaining at all. it was just a
simple question and a simple "no we won't continue to include php4 in
the portage tree, just put the ebuilds in a local overlay if you really
want to keep php4"-answer would have done the job.
and maybe your answer even motivated me to submit a gentoo-wiki article
about keeping depracted packages using a local repository. don't worry
i'll give you credit.
see, my question wasn't so stupid after all ;)
cheers,
take it easy
Andrew Gaffney wrote:
So...you know enough to run your ISP on Gentoo (at least I'd hope so),
but you think that the ebuilds being removed from portage will mean
you can no longer have php4? If you really want to keep it, stick the
ebuilds in an overlay and stop complaining.
Gentoo is removing the php4 ebuilds from the tree, because it won't be
security-supported by upstream very shortly. Gentoo doesn't have the
manpower to do security backports and such....we just bump to the next
version. Until you're paying to use Gentoo, please don't complain
about how the distro does things. Especially when the complaint it
"stupid".
Yves Thommes wrote:
i suppose we're not the only isp running gentoo and hosting sites like
this, and ezpublish is just an example, there are other cms/ecommerce
systems which don't run on php5. so please, just mask the php4 ebuilds
if you have to, but please don't remove them completely from portage.
thanks
A. Khattri wrote:
How ironic: Gentoo masks PHP4 because of a bunch of bugs and force a
lot of people to upgrade to PHP5. Then the PHP devs bring out bug
fixes for PHP4. So if we had waited we wouldn't have gone through the
pain of upgrading servers to PHP5...
--
[email protected] mailing list
