Conary normally refuses to build into a repository if the buildRequires are not satisfied. Normally, bootstrapping an OS has been done by a multi-stage bootstrap starting from a reasonably closely related OS where the same package names exist.
However, for this F20 RPM import, we will short-circuit that by building the initial packages from conary checkouts, with the buildRequires enforcement for building into a repository commented out until we have built enough native packages onto the common label (f20s1.flnx.org@f:20s-c) and imported enough RPMs onto the platform label (f20s1.flnx.org@f:20s) that we can satisfy build requirements from the repository. At that point, we'll be able to use rMake to drive the build process. Most of the required packages from the common label are not arch-flavored, such as the factories and base classes. Conary may be the only one that is arch flavored. We'll build Conary by checking source into the repository and then cooking it separately in the two chroots, one for each arch. We'll do the same for the initial RPM imports; importing them outside of Conary until we have the base package requirements fulfilled and can start using rMake. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
