Multilib conflicts in man pages.

Multilib conflicts in man pages.

[Jeremy Puhlman]

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.

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: Multilib conflicts in man pages.

[Jeremy A. Puhlman]

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
> 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.
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: Multilib conflicts in man pages.

[Richard Purdie]

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...

Cheers,

Richard

Re: Multilib conflicts in man pages.

[Jeremy A. Puhlman]

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...

Yeah, that works as well. Just need to brush up on my man-page-fu.

>
> Cheers,
>
> Richard
>
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: Multilib conflicts in man pages.

[Jeremy A. Puhlman]

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


> Cheers,
>
> Richard
>
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: Multilib conflicts in man pages.

[Richard Purdie]

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