I use the portage image (20040726) to install, followed by 'emerge sync', symlinking /etc/make.profile to /usr/portage/profiles/default-macos-10.3, 'emerge system', and 'emerge sed'. After that, I try 'emerge gentoolkit-dev' which fails with the following output:
!!! All ebuilds that could satisfy "portage" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-apps/portage-2.0.50-r8 (masked by: missing keyword)
- sys-apps/portage-2.0.50-r9 (masked by: missing keyword)
- sys-apps/portage-2.0.51_pre16 (masked by: package.mask)
# <firstname.lastname@example.org> (11 Apr 2004)
# Internal testing phase
- sys-apps/portage-2.0.51_pre17 (masked by: package.mask)
I can emerge the package using the --nodeps flag, however this doesn't solve the general problem. Adding sys-apps/portage-2.0.51_pre17 to /etc/portage/package.provided doesn't solve the problem (is this file not referenced?), though injecting sys-apps/portage-2.0.51_pre15 does.
You can install portage-2.0.51_pre17 on macos by
USE="build" FEATURES="-collision-protect" emerge \=sys-apps/portage-2.0.51_pre17
so something like this should be done in bootstrap-macos.sh?
The next installer will do the following:
1. install a portage version
2. install a portage tree
3. emerge portage with collision protection disabled
That way portage knows it is installed by when it gets installed by the installer. It also won't break knowledge about packages installed earlier by a possibly older version of portage
the problem is latest portage depends on debianutils which would install GNU auto* tools which would clash with the filesystem content anyway.
This bug (specifically, keywording portage macos) is blocked by 58823; the coreutils issue needs to be addressed/sorted out before portage will be keyworded macos.
Couldn't debianutils work with stuff already provided by OS X without installing additional coreutils?
Portage is keyworded for ppc-macos, so can we close out this bug, or are we waiting on the new installer?
*** Bug 67208 has been marked as a duplicate of this bug. ***
*** Bug 65713 has been marked as a duplicate of this bug. ***
*** Bug 64912 has been marked as a duplicate of this bug. ***
New installer solves this; yes, no?
Please reopen if needed.
Closing out bugs that've been resolved for a while now...