Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 12 Jul 2014 09:44:48 +0100
From: Laurent Bercot <>
Subject: Re: Status towards next release (1.1.4)

On 12/07/2014 08:24, wrote:
> For me it looks like you take a wrong kind of responsibility and try to
> make a decision which does not belong to a library developer.
> This is an "integrator" decision, the one who knows how the library will
> be used and what is the corresponding environment's policy of placing
> stuff around in the file system.
> In other words, as long as it is configurable, any "default" goes.
> You can not know (and imho do _not_ have to pretend to) what is best or
> sensible for the actual deployment.
> As an "integrator" I am concerned in the following way:
> - If locale is mostly static (additions or changes to locale
>    can be done at the same time as library recompilations/upgrades)
>    then a "default" placement is totally irrelevant, but I must be
>    able to choose the actual one at compilation time - I guess this is
>    expected and hence a non-issue

  +1 and QFT.
  Policy should not be included in software, but delegated to the user
(sysadmins and distributors). There should be a reasonable default, but
configurability is a lot more important than the exact default value.


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.