public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: toolchain@gentoo.org, base-system@gentoo.org
Subject: Update - Re: [gentoo-dev] glibc-2.26 and changes with SunRPC, libtirpc, ntirpc, libnsl (NIS and friends), ...
Date: Sat, 23 Sep 2017 23:05:04 +0200	[thread overview]
Message-ID: <2643322.oKTA8ZNROh@porto> (raw)
In-Reply-To: <1577962.20ZSkpDzGI@porto>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Update... 

So I asked ntirpc upstream, and they do not intend to remain compatible with 
sunrpc / libtirpc. Meaning we only have two RPC alternatives, one of which 
will go away, and things get a lot easier. 

> 1) About RPC.

https://wiki.gentoo.org/wiki/Project:Toolchain/RPC_implementation

^ please see this Wiki page for a proposed workflow and autoconf examples.

In short, IUSE=libtirpc switches the implementation, while IUSE=rpc switches 
an optional rpc support on/off.
(Similar to ssl, libressl)


> 2) About YP / NIS / NIS+.
> 
> a) The old libnsl implementation is provided by glibc, soversion 1.
> b) An updated and much improved implementation is provided by
> net-libs/libnsl, soversion 2.
> 
> glibc-2.26 installs only the library for a), and no headers.
> Since I dont want to mess with currently used glibc ebuilds, net-libs/libnsl
> requires at least our glibc-2.26 (otherwise you get file collisions).
> 
> Porting a package means adding a dependency in the style of

|| ( net-libs/libnsl <sys-libs/glibc-2.26 )



-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-09-23 21:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18  9:56 [gentoo-dev] glibc-2.26 and changes with SunRPC, libtirpc, ntirpc, libnsl (NIS and friends), Andreas K. Huettel
2017-09-18 12:28 ` M. J. Everitt
2017-09-18 15:36   ` Andreas K. Huettel
2017-09-18 15:40     ` M. J. Everitt
2017-09-18 15:45 ` Andreas K. Huettel
2017-09-18 18:51 ` Alexis Ballier
2017-09-18 19:57   ` Andreas K. Huettel
2017-09-19  5:06 ` [gentoo-dev] " Duncan
2017-09-19 12:53   ` Andreas K. Huettel
2017-09-20 18:33     ` Duncan
2017-09-19  7:14 ` [gentoo-dev] " Michał Górny
2017-09-19 18:44 ` Alexis Ballier
2017-09-19 20:38 ` [gentoo-dev] " Luca Barbato
2017-09-20  8:23   ` Andreas K. Huettel
2017-09-20  9:25     ` Michał Górny
2017-09-23 21:05 ` Andreas K. Huettel [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=2643322.oKTA8ZNROh@porto \
    --to=dilfridge@gentoo.org \
    --cc=base-system@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=toolchain@gentoo.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