rd <[EMAIL PROTECTED]> wrote: > If emerge -u world is trying to downgrade packages, you can > use /etc/portage.mask and /etc/portage.umask to set your > own permanent masks -- not trashed by an rsync.
This seems like a cleaner solution (other than portage working right <g>), but I'm having trouble. I created a file containing only the line: >=tcl-8.4 And tried naming it: /etc/portage.umask /etc/portage.unmask /etc/portage/package.umask /etc/portage/package.unmask /etc/portage/portage.umask /etc/portage/portage.unmask (those last two were clearly a shot in the dark) But when I try `emerge -pv \>=/dev-lang/tcl-8.4', I still get the message: !!! all ebuilds that could satisfy ">=/dev-lang/tcl-8.4" have been masked. Which leads me to conclude that my unmasking isn't working. > Somewhere on the forums there is a sticky topic about this > relatively new emerge/portage feature. It was looking around the forums that created the confusion over what this file should be named. Every reference I found used something different. I'm using portage-2.0.49-r15. -Eamon -- [EMAIL PROTECTED] mailing list
