public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Rical Jasan <ricaljasan@pacific.net>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] ldconfig: set LC_COLLATE to C
Date: Mon, 27 Nov 2017 09:23:00 -0000	[thread overview]
Message-ID: <20171127092340.vnzaybitnf5nhtyc@aurel32.net> (raw)
In-Reply-To: <44ff342a-e130-d6ed-c609-9179c78fc58a@pacific.net>

On 2017-11-28 00:47, Rical Jasan wrote:
> On 11/26/2017 03:32 AM, Aurelien Jarno wrote:
> > ldconfig supports "include" directives and use the glob function to
> > process them. The glob function sort entries according to the LC_COLLATE
> > category. When using a standard "include /etc/ld.so.conf.d/*.conf" entry
> > in /etc/ld.so.conf, the order therefore depends on the locale used to
> > ldconfig. Prefixing the files that have to be processed last with "z"
> > or "zz" (as it is often used) therefore doesn't work correctly as "z"
> > is not always the last letter. For example in the et_EE locale, it is
> > sorted after the "s".
> 
> Did you mean before the "s"?

More precisely just after the "s" or between the "s" and the "t".

> But wouldn't the user/admin expect the files to be sorted according to
> their locale?

There might be more than one admin on the system using different
locales. In addition to that ldconfig can be launched by system scripts
using a different locale.

> If a strict ordering is needed, I would expect numerical
> prefixing to be used.

In practice distributions ship file in /etc/ld.so.conf.d, so it's not
something fully in control of users. On Debian and Fedora for example
they start with letters. And depending on the locale, numerical prefixes
might be sorted before or after letters.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2017-11-27  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 11:32 Aurelien Jarno
2017-11-27  8:48 ` Rical Jasan
2017-11-27  9:23   ` Aurelien Jarno [this message]
2017-11-27  9:45   ` Andreas Schwab
2017-11-27 16:21 ` Joseph Myers
2017-11-27 16:36 ` Carlos O'Donell
2017-11-27 17:02   ` Florian Weimer
2017-11-27 17:15     ` Carlos O'Donell
2017-11-27 17:16       ` Florian Weimer
2017-11-27 17:28         ` Carlos O'Donell
2017-11-27 20:35   ` Aurelien Jarno

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=20171127092340.vnzaybitnf5nhtyc@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=libc-alpha@sourceware.org \
    --cc=ricaljasan@pacific.net \
    /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).