When building OpenBMC . . . ?

[Patrick Voelker]

I'm giving the first option below a try.  I've defined an alternative variant and have included the meta-facebook/meta-tiogapass layer in my build.

One problem I'm running into is that meta-tiogapass includes a rsyslog*.bbappend and one of the other layers I'm using also has a similar rsyslog*.bbappend.

Each do an append to do_install() and each one tries to remove ${D}${sysconfdir}/rsyslog.d/imjournal.conf.  Of course that file can only be removed once so the build fails.

My question now, is what's the best way to work around this?  I don't need rsyslog from meta-tiogapass, just the machine specifics.


> -----Original Message-----
> From: openbmc [mailto:openbmc-
> bounces+patrick_voelker=phoenix.com at lists.ozlabs.org] On Behalf Of Ed
> Tanous
> Sent: Tuesday, September 1, 2020 9:10 AM
> To: Patrick Williams
> Cc: Bruce Mitchell; openbmc at lists.ozlabs.org
> Subject: Re: When building OpenBMC . . . ?
> 
<snip>
> > #1 should go into meta-phoenix.  You're likely the first one doing this,
> > so we may need some experimentation on the best option.  I have two
> > ideas (there are probably others):
> >
> >   * Make an alternative tiogapass variant, like tiogapass-phoenix, which
> >     ends up including all the common tiogapass code from meta-facebook.
> >
> >   * Create a new distro type for phoenix, which enhances the underlying
> >     openbmc distribution with your own branding tweaks.  You'd still
> >     build meta-facebook/tiogapass but with a different distro flavor.
> 
> This one would be my vote between the two, and I think there's
> precedent with other companies doing similar things.  Isn't this the
> way yocto recommends?