From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>, libc-alpha@sourceware.org
Subject: Re: nss_compat still deprecated?
Date: Wed, 20 Jun 2018 13:10:00 -0000 [thread overview]
Message-ID: <8d8835b6-0a2c-4306-5011-61acbb6c30ac@redhat.com> (raw)
In-Reply-To: <8736xi0x1a.fsf@mid.deneb.enyo.de>
On 06/20/2018 02:52 AM, Florian Weimer wrote:
> Did we un-deprecate nss_compat? Should we?
>
> Since this commit:
>
> commit 64d1e08ea822bf47cb2796ad0f727136227f983c
> Author: Andreas Schwab <schwab@suse.de>
> Date: Mon Oct 2 14:30:46 2017 +0200
>
> Move nss_compat from nis to nss subdir and install it unconditionally
>
> This has been tested that local lookup still works with and
> without an installed libnss_nis, and that NIS lookup works when
> libnss_nis is available.
>
> it is no longer necessary to deprecate nss_compat because there is no
> strong (non-configurable) NIS dependency anymore.
>
> If we un-deprecate nss_compat, we should add a note to NEWS (both for
> 2.28 and 2.27.1).
>
We have reports of at least 2 customers using compat for useful
purposes because of the way it allows you to alter the lookup
results at a local level e.g. local override.
If we "un-deprecate" it then we should review the manual information
and the linux man page documentation and update it to match the most
recent behaviour.
I'm in favour of un-deprecating it.
Cheers,
Carlos.
prev parent reply other threads:[~2018-06-20 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 7:58 Florian Weimer
2018-06-20 13:10 ` Carlos O'Donell [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=8d8835b6-0a2c-4306-5011-61acbb6c30ac@redhat.com \
--to=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).