[OE-core] Multilib conflicts in man pages.

Richard Purdie richard.purdie at linuxfoundation.org
Fri Mar 6 22:31:11 UTC 2020


On Fri, 2020-03-06 at 14:14 -0800, Jeremy A. Puhlman wrote:
> 
> On 3/6/2020 2:00 PM, Richard Purdie wrote:
> > On Tue, 2020-03-03 at 15:22 -0800, Jeremy Puhlman wrote:
> > > Is there a preferred method in oe-core for dealing with man pages
> > > that conflict due to differences in multilib pathing.
> > > 
> > > For example an application lives in /usr/lib/foo/bar for one abi
> > > but
> > > /usr/lib64/foo/bar in another, and
> > > that kind of information is encoded in to the man pages.
> > > 
> > > Some things i have seen done in the past, is move the man pages
> > > under
> > > /user/share/man/${PN} or
> > > use something like mutlilib script to deal with it.
> > > 
> > > I am just curious if there is a canned, preferred way the project
> > > handles those or wants to handle them?
> > > 
> > > xinit, xserver-org, and groff each exhibit  these issues.
> > Could we just put a placeholder into the man page so they'd be
> > identical? Multiple copies seems like overkill for something as
> > trivial...
> 
> A placeholder like:
> /usr/<system libdir>/sys.startxrc
> from
> /usr/lib64/sys.startxrc

Yes, not sure about the exact form. You could just do:

/usr/lib*/sys.startxrc
or
/usr/<libdir>/sys.startxrc

?

Cheers,

Richard




More information about the Openembedded-core mailing list