It's finally time, I think, to prune CVS. The prune would only involve e17/. e16/ is fine, I already pruned web/ awhile back, and misc is supposed to be a mess. This means we need to confront some issues we've been avoiding for awhile, like: Should we migrate proto/ into libs/ ? Do we whack the old dead apps? (etcher, e, etc)
My initial hit list of things to go are: libs/ebg libs/ebits libs/emenu libs/eprog libs/evas2 libs/imlib2_loader_db apps/ebindings apps/efm apps/efileinfo apps/elogin apps/esmall apps/etcher apps/ewidgetd apps/foo apps/med apps/ebony Okey, some of these are questionable. Like, would anyone ever be interested in resurecting Ebits? Someone from outside the project might. Which means Ebony and Etcher would be handy. Do we whack E? Or leave it for historical reference in the rewrite? When we do that whack I'll make a backup using the nightly CVS tar (which is the raw cvsroot itself) just in case we change our minds later. If anyone thinks maybe it's too early to clean up CVS thats valid too. Project owners!: Any directories inside your code that need to be pruned please let me know about. benr. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
