All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] readline/ediline: Fix conflicting manpages.
Date: Tue, 25 Feb 2020 15:34:11 +0100	[thread overview]
Message-ID: <bf82e526-a78b-14b7-42cc-b5fbb467e35b@gmail.com> (raw)
In-Reply-To: <42d690f3ae40a420179cb85453d2722c153c2d8c.camel@linuxfoundation.org>

On 2/25/20 2:33 PM, Richard Purdie wrote:
> On Tue, 2020-02-25 at 14:08 +0100, Jacob Kroon wrote:
>> On 2/22/20 7:54 PM, Jeremy A. Puhlman wrote:
>>>    BBCLASSEXTEND = "native nativesdk"
>>> +
>>> +inherit update-alternatives
>>> +
>>> +ALTERNATIVE_PRIORITY = "90"
>>> +ALTERNATIVE_${PN} = "history.3"
>>> +ALTERNATIVE_LINK_NAME[history.3] = "${mandir}/man3/history.3"
>>>
>>
>> With this change (I think), I now get a file
>>
>>> +lrwxrwxrwx root       root               38
>>> ./usr/share/man/man3/history.3 ->
>>> /usr/share/man/man3/history.3.readline
>>
>> in my rootfs, which is wierd since I don't have any other man pages
>> in my image..
> 
> At a guess, ALTERNATIVE_${PN} should be ALTERNATIVE_${PN}-doc ?
> 

I can confirm that changing the recipe according to RP's suggestion gets 
rid of that file in my image.

Thanks,
Jacob


      reply	other threads:[~2020-02-25 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22 18:54 [PATCH] readline/ediline: Fix conflicting manpages Jeremy A. Puhlman
2020-02-25 13:08 ` Jacob Kroon
2020-02-25 13:33   ` Richard Purdie
2020-02-25 14:34     ` Jacob Kroon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf82e526-a78b-14b7-42cc-b5fbb467e35b@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.