On 7/17/09, Mick michaelkintz...@gmail.com wrote:
Hi All,
I didn't have to do this before, so will need help to manage portage:
A particular package has been hard masked for removal. I would like
to either move it in my local portage, or even better emerge a more
recent version. So, I found an ebuild, modified it a bit and now I am
trying to emerge it, but it seems that the package.mask won't let me:
=
!!! The following installed packages are masked:
- app-pda/plptools-0.13 (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Jeremy Olexa darks...@gentoo.org (30 May 2009)
# Masked for removal in 60 days. Doesn't build, version bump pending.
Designed
# for really old PDA hardware (circa '90s) - will need a maintainer that has
# hardware. bug 227601
=
I am trying to emerge v1.0.8, not 0.13 as shown above. Should the
above mask stop me emerging it from my local overlay? How do I allow
a local overlay emerge, while respecting portage's hard mask for
ebuilds in the main tree only?
man portage:
package.unmask
Just like package.mask above, except here you
list packages you want to unmask. Useful for overriding the global
package.mask file (see
below). Note that this does not override
packages that are masked via KEYWORDS.
So, add app-pda/plptools to /etc/portage/package.unmask to remove
package.mask blocks from affecting the emerge calculation for that
package -- and if you're running stable arch and the package only has
~arch, also add ~arch for your package in
/etc/portage/package.keywords (or edit your own ebuild, as in your own
overlay you can decide if it is stable or not).
If portage still doesn't offer to emerge v1.0.8 after doing those you
still may have something wrong with your local overlay / ebuild. Did
you digest/manifest the ebuild you copied to the local overlay? Is the
local overlay added properly in /etc/make.conf (no typos in path etc)?
--
Arttu V.
