Cross-architecture package installs
brooks at FreeBSD.org
Sun Feb 10 11:12:08 UTC 2013
On Wed, Feb 06, 2013 at 06:20:22AM -0700, Ian Lepore wrote:
> On Tue, 2013-02-05 at 22:34 -0800, Tim Kientzle wrote:
> > I'm working on tools to build ARM system images.
> > Usually, these tools run on x86, which creates a problem
> > for packages.
> > I would like to install packages onto the image as it's built.
> > So I've been experimenting with variations of
> > pkg -c <DESTDIR> add <package files>
> > I'm running into a few problems but I think they can all be
> > solved. Only the first is critical; the rest are relatively
> > minor annoyances.
> > 1) Pre-install/post-install scripts.
> > These obviously don't work since the DESTDIR
> > is for a different architecture.
> > At least for post-install, it should be possible to
> > record which packages still need their post-install
> > scripts run and arrange to run them after first
> > boot. I'm picturing an rc.d script that invokes pkg
> > with appropriate options to find all packages
> > that still need their post-install run and runs them.
> > This won't work for pre-install, but those are rarer
> > and we can hopefully work around them on a
> > case-by-case basis.
> > 2) The chroot happens before opening the package files.
> > It's possible to work around this by copying all of the
> > package files into DESTDIR first, but that's both
> > time-consuming and rather awkward. (And quite
> > tricky if you're installing directly onto a mounted
> > image that has very little free space.)
> > It should be feasible to open the package files first
> > and then chroot. Then the actual installation still
> > happens entirely inside DESTDIR.
> If you have a directory full of the package files, you can nullfs-mount
> it within the chroot rather than copying its contents in. Nullfs mounts
> are great for crossing chroot barriers in such situations.
> Using them does make your scripts more complex, because you need abort
> and exit handling in the scripts to undo the mounts no matter what kind
> of exit the script encounters. If you don't, you end up leaving nullfs
> mounts that make later things fail (such as running the script again, or
> trying to clean/remove a chroot tree).
I'd rather avoid nullfs since it requires root or at least enabling user
If one wanted to avoid opening all packages to start off, just opening
the package directory and using dirfd() and openat() to do opens later
could also work. Without looking at the pkg code it might require
fewer changes to the existing code flow.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 188 bytes
Desc: not available
More information about the freebsd-current