On Friday 03 April 2009 23:46:44 Mark Knecht wrote: > 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'd like a way to completely lock a package to the current running version, and be able to do something like this: emerge --lock <some-package-some-version> emerge could then move the ebuild to a local overlay, mask out higher versions, and remember the original ebuild source (portage tree|overlay) and keep checking back in for -r updates. This would let people lock video drivers to a certain version while still getting -r* bug-fix updates. It would fix the problem of having to go and fetch ebuilds from a repo after they have been uninstalled. It would also fix my current issue of having to closely inspect emerge output to make sure that KDE-4 ebuilds are coming from the tree, not the overlay. -- alan dot mckinnon at gmail dot com
