On Thu, Jul 2, 2015 at 12:55 PM, Philip Balister <[email protected]> wrote:
> I'm going round and round thinking about creating custom ntp.conf files. > > The existing recipe includes an ntp.conf file. My question is what is > the best way to replace the on from the recipe with a machine specific > config. > > There are a couple of config issues: > > 1) hardware may want to sync with an on board gps > 2) A vendor may want to use their own ntp servers. > > Obviously, these need to apply only to specific machines and not all > builds from the same set of layers. > > Any ideas how to do this without making the entire ntp package machine > specific? > > Should we split the conf file into a separate recipe, sort of like gpsd? > Afaik that’d be the best way to handle it, iirc that’s how connman and the like handle it too. Also remember to add it to SIGGEN_EXCLUDERECIPES_ABISAFE in meta/conf/layer.conf if you go that route, so stuff depending on it doesn’t get unnecessarily rebuilt when it changes. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
