[Buildroot] custom skeleton question

[Peter Korsgaard]

>>>>> "Liam" == Liam Staskawicz <liam at stask.net> writes:

Hi,

 >>> I'd like to create a custom rootfs skeleton based on Ubuntu Base
 >>> (https://wiki.ubuntu.com/Base) via the existing skeleton-custom
 >>> package, but rather than ship the entire skeleton in my repo, i'd like
 >>> to download it (either as a step in another custom package or
 >>> otherwise).
 >> 
 >> Doesn't this "base" already contain a number of libraries and programs?
 >> I don't quite see how this fits in Buildroot.
 >> 
 >>> Given that BR2_ROOTFS_SKELETON_CUSTOM_PATH is evaluated at kconfig
 >>> time, I don't see the best way to supply this value from another
 >>> package.
 >> 
 >>> Is there a recommended approach to supply this value more dynamically?
 >> 
 >> Instead of using it as a rootfs skeleton you could perhaps create a
 >> package to download such a "base" and extract it on top of the default
 >> skeleton?

 > Thanks for the response. I can indeed investigate overlaying it on the
 > default skeleton - mainly wanted to confirm I was not missing an
 > intended way to use the existing skeleton-custom mechanism with a more
 > dynamically supplied custom path. Thank you.

Ok - But again, if the Ubuntu base image contains a bunch of prebuilt
binaries and library you may very well end up with odd errors if you try
to merge them with Buildroot.

What are you trying to achieve here?

-- 
Bye, Peter Korsgaard