On Fri, 2005-08-26 at 23:29 +0100, Neil Bothwick wrote:
> That's irrelevant. Portage keeps the ebuilds used to install each
> package
> in /var/db/pkg. Otherwise updating a deprecated package would be
> impossible. The problem is that the ebuild uses an eclass that no
> longer
> exists.

Bingo.

I had to go to viewcvs and get the old php.eclass and then I was able to
unmerge.

I suppose it would have been nice if one day when I was doing esync,
that I was warned php.eclass would be gone. And here are the merges you
have done which are covered by that: etc.

-- 
[email protected] mailing list

Reply via email to