Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Markus Mohrhard wrote:
Can you explain what you had in mind with the config layer idea.

Largely just avoiding duplicated code (no need to xml-parse, do
layering etc).

I don't see the values as I doubt many admins will be able to change
it and I had hoped that it would be enough to provide a config entry
that points the local location of the blacklist.

Well, it's just the principle of least surprise - all standard config
deployment/overriding/lockdown mechanisms would then simply work. Also
- as always, there'll be at least *one* person wanting to do special
magic ... ;)

So if a admin really wants to disable access to it he puts the
blacklist in a place where the user can't touch it and lock the
setting.

Fair enough. Doesn't make group policies / machine-specific settings
extra-easy, but I guess it'll work.

Cheers,

-- Thorsten

Attachment: signature.asc
Description: Digital signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.