On Thu, Jun 22, 2017 at 9:33 AM, Neal Gompa <ngompa13@xxxxxxxxx> wrote: > On Thu, Jun 22, 2017 at 9:29 AM, John Reiser <jreiser@xxxxxxxxxxxx> wrote: >> On 06/22/2017 0013Z, Neal Gompa wrote: >>> >>> Yes, we do have debootstrap, but it can only build Debian-based systems. >>> :) >>> >>> I want to be able to build a Fedora based one. >> >> >> Please be specific, and give a concrete example of what should change. >> >> debootstrap takes a list of .debs and builds a root filesystem that contains >> them. >> febootstrap takes a list of .rpms and builds a root filesystem that contains >> them. >> In both cases the result contains some distro-specific metadata as files: >> the packaging data for maintenance of the system, which is implicit >> (are not files that are contained in some input .debs or .rpms.) >> In the case of Debian, the "extra" info is the apt metadata. >> In the case of Fedora, the "extra" info is the dnf/yum metadata. >> >> Anything else? >> > > debootstrap has the capability to utilize qemu-user-static to support > constructing foreign arch rootfses. That means I can build an arm64, > armhf, or ppc64el rootfs from an x86_64 host. As far as I know, > febootstrap can't do this. > > The missing piece here is that I want to be able to construct a rootfs > or an image for an architecture that *isn't* the same as my host > machine. For what purpose? josh _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
