This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Remove compat from DEFAULT_CONFIG lookup strings


On Fri, 18 Aug 2017, Steve Ellcey wrote:

> On Fri, 2017-08-18 at 21:12 +0000, Joseph Myers wrote:
> > On Fri, 18 Aug 2017, Steve Ellcey wrote:
> > 
> > > 
> > > I would think so.  I did a search and didn't find any more "compat"
> > > lookups beyond what you found.  Not doing these changes didn't cause
> > > any testsuite failures but it does seem like they should be changed.  I
> > > updated them and reran the testsuite and got no regressions.  Here is
> > > an updated patch.
> > Does this affect any defaults visible to glibc users?  If it does, it 
> > needs an entry in the "Deprecated and removed features, and other changes 
> > affecting compatibility" section of NEWS.
> 
> I think everything is already in the 2.26 Depreciated section.  This
> was done when the original patch to remove libnss_compat was made.
> These changes are just dealing with the fact that that patch was
> incomplete.

But the impression that NEWS entry gives is that you can use 
--enable-obsolete-nsl to get back the previous semantics.  Does your patch 
change the semantics in the --enable-obsolete-nsl case?

-- 
Joseph S. Myers
joseph@codesourcery.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]