public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paulo Neves <ptsneves@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v3 1/2] ntirpc: Add ntirpc recipe
Date: Thu, 15 Sep 2022 13:18:46 +0200	[thread overview]
Message-ID: <4084d4d1-5cc4-fdb7-0c26-543dfd30c1b4@gmail.com> (raw)
In-Reply-To: <C8950D71-C267-4624-A510-E0F81BFB4FD2@arm.com>

libntirpc is not compatible with libtirpc. Some work would make it so, 
but it is not a trivial change, i tried it :)

Not only the API is different, the pkgconfig presents itself as ntirpc 
whereas most dependencies of litbtirpc specifically try to detect 
libtirpc. A good summary of the differences and the feasibility is in 
this page [1].

I can break the extending of liburcu into another commit no problem.

I was able to break the circular dependency as well, with a patch that 
is already for review upstream.

[1] https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1843403

On 9/15/22 12:50, Ross Burton wrote:
> On 28 Aug 2022, at 18:43, Paulo Neves via lists.openembedded.org <ptsneves=gmail.com@lists.openembedded.org> wrote:
>> ntirpc is an actively maintained rpc implementation. We cannot completely
>> remove libtirpc due to arising circular dependencies where ntirpc
>> depends on libnsl2, which in turn depends on an RPC implementation.
> Can you split this into a series of commits?  Extend liburcu, add ntirpc, update the recipes to use ntirpc.
>
> Ross



      reply	other threads:[~2022-09-15 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 17:43 [PATCH v3 1/2] ntirpc: Add ntirpc recipe Paulo Neves
2022-08-28 17:43 ` [PATCH v3 2/2] nfs-ganesha: Replace unfs3 with nfs-ganesha Paulo Neves
2022-08-28 19:13   ` [OE-core] " Alexander Kanavin
     [not found]   ` <170F981B9326E578.11791@lists.openembedded.org>
2022-08-28 19:15     ` Alexander Kanavin
2022-08-29  9:20   ` Alexandre Belloni
2022-09-12 22:19   ` Adrian Freihofer
     [not found]   ` <17143CF1C30D4B98.24896@lists.openembedded.org>
2022-09-14 21:19     ` Adrian Freihofer
2022-09-15  7:28       ` Paulo Neves
2022-08-28 19:07 ` [OE-core] [PATCH v3 1/2] ntirpc: Add ntirpc recipe Alexander Kanavin
2022-09-15 10:50 ` Ross Burton
2022-09-15 11:18   ` Paulo Neves [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=4084d4d1-5cc4-fdb7-0c26-543dfd30c1b4@gmail.com \
    --to=ptsneves@gmail.com \
    --cc=Ross.Burton@arm.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox