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
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
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
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
>
Anyone have a thought?
On 3/3/2020 3:22 PM, 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
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
