Hani Duwaik wrote:
Have you tried the suggestion outlined at:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
Yes, that is just normal package masking. Maybe I should elaborate.
I like to update daily. When the occasional blocker or cyclic dependency
hit, I'd like to simply mark it (generate bug report if necessary), and go
on. Where I find myself failing with the package.mask approach is
remembering some time in the future to go back and remove these
temporary masks.
So I was querying if there is a better process. Some way to tickle
that the ebuild that caused the problem has been upgraded and that
I should unmask the package.
Thank you,
Roy
--
gentoo-user@gentoo.org mailing list
