I added the line: app-admin/logrotate ~mips to my /etc/portage/package.keywords file. However, an 'emerge -p logrotate' still showed logrotate as being masked for my mips architecture. Only by modifying the logrotate ebuild could I get logrotate to emerge. Reproducible: Always Steps to Reproduce: 1. (on mips arch): emerge -p logrotate 2. 3. Actual Results: These are the packages that I would merge, in order: Calculating dependencies !!! all ebuilds that could satisfy "logrotate" have been masked. !!! possible candidates are: - app-admin/logrotate-3.6.5-r1 (masked by: missing keyword) !!! Error calculating dependencies. Please correct. Expected Results: These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] app-admin/logrotate-3.6.5-r1 Portage 2.0.50-r9 (default-mips-2004.1, gcc-3.4.0, glibc-2.3.3_pre20040420-r0, 2.6.6-rc3) ================================================================= System uname: 2.6.6-rc3 mips64 R12000 V2.3 FPU V0.0 Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="mips ~mips" AUTOCLEAN="yes" CFLAGS="-O2 -mips4 -mabi=32 -fomit-frame-pointer -pipe" CHOST="mips-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mips4 -mabi=32 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="ccache keeptemp keepwork" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://fizban:8730/gentoo-portage" USE="apache2 berkdb crypt cups doc gd gdbm gif gpm ipv6 jpeg libwww mips nls pam perl png python readline sdl slang spell ssl tcpd truetype xml xml2 zlib"
Telling it to accept ~mips as a keyword isn't going to do anything when logrotate doesn't have a ~mips keyword. package.keywords is working as it should; it just isn't having the effect you expected. Try 'app-admin/logrotate x86', since logrotate actually has an x86 keyword.
Then how does it work? I read the portage man page for package.keywords, both before adding the line to package.keywords, after; and again after getting your response. It still doesn't seem to make sense. So, from what you are saying - it seems as if the package.keywords file will allow one to specify what ACCEPT_KEYWORD to use when considering the given package, correct? So, if I added 'add-admin/logrotate ~x86' to the file - I am effectively telling portage that when considering logrotate, to think of my system as an ~x86 one? (But then it will build as ~mips, right?) And yes - I agree - this could very easily be a simple case of OE. Thank you for your prompt response.
This is probably not a dev-portage bug. mips team.. Can you please test and keyword logrotate.
portage(5) package.keywords <SNIP> This will allow you to augment ACCEPT_KEYWORDS for a single package.
Jason, Yes - I read that. And that is exactly what did *not* happen. I was expecting it to augment ACCEPT_KEYWORDS in the logrotate ebuild with what I added to package.keywords. It did not do this. I believe the documentation describes some other behavior than reality.
no, it describes the correct behavior you're *expecting* different behavior than what's happening package.keywords just adds values to your ACCEPT_KEYWORDS for specific packages ... in this case, when you tried to merge log rotate, it looked like this: logrotate:KEYWORDS="~x86" you:ACCEPT_KEYWORDS="mips ~mips" notice how they do not match
Ahh!! (light-bulb over head).. :) Thank you. Now I understand. And, as is usual in the case of OE - I feel a bit sheepish. Again, thanks. Sorry to trouble everyone.
