On Friday 01 June 2012 19:24:54 Christopher Larson wrote:
> Both rpcbind and portmap are RPC port mappers. Having both is redundant.
> Chose rpcbind over portmap as rpcbind supports ipv6, nfs4, and builds
> without the glibc rpc headers, which have been obsoleted in glibc 2.14.
> 
> Signed-off-by: Christopher Larson <kerg...@gmail.com>
> ---
>  meta/recipes-extended/tasks/task-core-basic.bb |    1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/tasks/task-core-basic.bb
> b/meta/recipes-extended/tasks/task-core-basic.bb index 8bab0db..a810d37
> 100644
> --- a/meta/recipes-extended/tasks/task-core-basic.bb
> +++ b/meta/recipes-extended/tasks/task-core-basic.bb
> @@ -148,7 +148,6 @@ RDEPENDS_task-core-sys-services = "\
>      nfs-utils \
>      pciutils \
>      libpcre \
> -    portmap \
>      rpcbind \
>      sysfsutils \
>      tcp-wrappers \

I came across this while digging back through the history in master. Does this 
mean we ought to be switching to rpcbind in our other tasks which currently 
bring in portmap (e.g. task-base-nfs, task-core-apps-console)?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to