Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140722203648.GB11570@brightrain.aerifal.cx>
Date: Tue, 22 Jul 2014 16:36:48 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Locale bikeshed time

On Tue, Jul 22, 2014 at 09:17:50PM +0100, Laurent Bercot wrote:
> 
> >So, the first bikeshed decision to be made is what environment
> >variable to use for the locale path, and what fallback should be if
> >it's not set. Glibc uses $LOCPATH. On the one hand it would be nice to
> >use the same var (since apps are already aware of the need to treat it
> >specially), but on the other it's undesirable to have them tied
> >together (e.g. if you're using musl as a non-root installation and
> >can't write to /usr/lib) and to avoid clashing with glibc's files we
> >would need to choose a subdirectory under $LOCPATH rather than using
> >it directly. All of these aspects make it a lot less attractive.
> 
>  Well, my suggestion is going to be ugly, but it's the most flexible
> one: have two variables. LOCPATH for compatibility, and something
> like MUSL_LOCPATH for admins who fear conflicts. Try $MUSL_LOCPATH
> first, then fallback to $LOCPATH if MUSL_LOCPATH is not set, then
> fallback to a hard-coded directory.

Do you have in mind a usage case this would be beneficial for?

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.