If the full path to an ebuild file is given, Portage will ignore any masks and emerge the package. I am not sure if this behavior is intended, but for the sake of consistency emerge should behave identically no matter how one identifies the package and version to be installed. The currently-available Portage documentation does not suggest that there should be any differences in package processing as a result of how the package is identified by the user. Reproducible: Always Steps to Reproduce: 1. Locate a package which is masked either in package.mask or flagged as unstable in its ebuild script. 2. Attempt to emerge that package version using the '=package-ve.rs.ion' notation. 3. Attempt to emerge that same package version using the full path to its ebuild file. Actual Results: root@blackbox sys-apps # emerge =gradm-1.7b Calculating dependencies !!! all ebuilds that could satisfy "=gradm-1.7b" have been masked. !!! Error calculating dependancies. Please correct. root@blackbox sys-apps # emerge /usr/portage/sys-apps/gradm/gradm-1.7b.ebuild Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/gradm-1.7b to / >>> Downloading http://distro.ibiblio.org/gentoo/distfiles/gradm-1.7b.tar.gz Expected Results: If the user has not enabled non-stable builds, emerge should fail no matter how the build is referenced. Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.20-gentoo-r1 i686 AMD Athlon(tm) processor GENTOO_MIRRORS="http://distro.ibiblio.org/gentoo http://mirrors.sunsite.dk/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.ibiblio.org/pub/linux/distributions/gentoo http://gentoo.oregonstate.edu ftp://ftp.oregonstate.edu/pub/gentoo " CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/conf ig /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm arts avi crypt cups encode gif gpm gtk imlib jpeg kde gnome libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime sdl spell svga truetype xml2 xmms xv zlib gdbm berkdb slang readline java mysql X tcpd pam ssl perl python oggvorbis qt motif opengl" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-O2 -mcpu=i686 -pipe" CXXFLAGS="-O2 -mcpu=i686 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
this is intended behaviour; the docs team should update the docs
Created attachment 9587 [details, diff] Proposed documentation patch Possible explanation of functionality when emerging from an ebuild file reference
I will look into this.
Patch looks good. Committed.
