Summary: | macos: portage does not know it is installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nick Dimiduk (RETIRED) <ndimiduk> |
Component: | [OLD] Core system | Assignee: | osx porters <osx> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | CC: | bugs+gentoo, clmason, czhang.cmu, hansmi, pvdabeel, rmunn, sah.list, syktek, wufrxl902 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 58823, 59479, 60468 |
Description
Nick Dimiduk (RETIRED)
2004-08-08 17:19:12 UTC
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... |