Jorge Manuel B. S. Vicetto wrote:
> Hi.
> 
> As the KDE team prepares to add revised eclasses for the KDE3 ebuilds so
> we can get 3.5.10 marked stable and then finally ask for KDE4
> stabilization, we'd like to drop some old eclasses from the tree. We
> plan to drop the kde-base, kde-dist, kde-i18n and kde-source eclasses as
> they're no longer used.
> So unless someone has any objections, we'll drop the eclasses from the
> tree in the next few days.
> 
> In case anyone has any doubts about portage reliance on the eclasses,
> let me quote Zac:
> 
> #gentoo-dev 20:19 <@zmedico> jmbsvicetto: it's only an issue for people
> upgrading from less than portage-2.1.4, which is pretty rare nowadays
> 
> 
> For the KDE team,
> 

It's an issue for people who have packages in vdb emerged with portage
older than 2.1.4 (if this was the version where the env started being
added to vdb). I have been maintaining the position that nuking eclasses
doesn't really provide enough benefits to bork these installs. I
recommend just making the eclasses unusable for emerging stuff and
keeping uninstalls working.

Regards,
Petteri

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to