FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

LinkBack Thread Tools
Old 11-30-2009, 04:19 PM
Tomáš Chvátal
Default RFC: Removing eclasses

Currently the approach is that you must mark the eclass as deprecated and wait
2 years in order to remove it.

I would propose to do it more fine grained.

Since portage the environment is stored and preserved, thus eclasses
are no longer required for package uninstalls (which is the only reason for
above rule).

Bit research for history here when or later was stabilised reveals the
date Mon Feb 18 09:51:22 2008 UTC. [1]
As we can say everyone even stable people potentialy update to before 1st
August during individual updates. We can safely assume that after 4 months
noone use individual commands and gets it grabbed using @world or @system
target. So we can set the date on:

So we can have 2 case scenario here now.

Eclass is newer than this date
It can be removed right away since portage is using the environment, thus the
eclass would be just wasting space and looking ugly :P

Eclass is older than the date
Here we need to find out if it is used, and if it is used it needs to go full
2 years period before removal.
If it is no-longer used, the 2 years period started ticking when the last
ebuild using such eclass was in main tree.


[1] - http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-

Tomáš Chvátal
Gentoo Linux Developer [KDE/Overlays/QA/Sunrise/X11]
E-Mail : scarabeus@gentoo.org
GnuPG FP : 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587
GnuPG ID : 03414587

Thread Tools

All times are GMT. The time now is 11:31 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org