On Fri, Apr 3, 2009 at 2:38 PM, Mark Knecht <markkne...@gmail.com> wrote: > On Fri, Apr 3, 2009 at 2:21 PM, Volker Armin Hemmann > <volkerar...@googlemail.com> wrote: > <SNIP> >> >> portage does not remove the packages from the distfiles directory and all >> ebuilds are available from cvs even years after they have been removed. >> > > First comment is incorrect, or correct if you're doing your regular > Volker routine and think I should have said emerge instead of portage. > None the less, packages that have been depreciated are first removed > from portage and then when I run eix-sync are removed from my system, > and have been for years now. > > ebuilds are available long after tha package has been depreciated. > Probably the actual code is available also. That said, once given to > me and put into use on my system it shouldn't be taken off my system > without permission just because someone doesn't want to support it. > (Even for security reasons. Even that should be my business, but I > understand others will have other opinions on this part.) > > Even a flag that stated what revision I don't want to have removed > would be better than what goes on right now. > > - Marl > Volker, I apologize for speaking quite so strongly here. No reason for me to have done that.
I think you may be correct, but the problem still exist. The problem is that you can be running an driver on your system. The portage maintainers depreciate it. the ebuilds get stripped form my machine. Sometime later I choose to clean up distfiles and delete the driver, thinking I can download it again because the version I'm running is masked to be the only one I want. I do an emerge sync and find out it's no longer in portage and have to do a lot of work to get it back again. I think portage could be far more nuanced in this area if it noticed what I was actually running on the system and moved a copy of everything somewhere on my system to keep me safe. Again, I apologize for speaking so strongly. Your consistent better-than-others tone sets me off, but that's no reason for me to react publicly. My bad. Mark
