[Nut-upsdev] [nut-commits] svn commit r2588 - branches/windows_port/common

[Arnaud Quette]

2010/10/20 Frédéric Bohé

> On mer., 2010-10-20 at 11:24 +0200, Arjen de Korte wrote:
> > Citeren Frederic BOHE <fbohe-guest at alioth.debian.org>:
> >
> > > Author: fbohe-guest
> > > Date: Wed Oct 20 09:13:38 2010
> > > New Revision: 2588
> > > URL: http://trac.networkupstools.org/projects/nut/changeset/2588
> > >
> > > Log:
> > > Remove hack from confpath function. You have to declare a
> > > NUT_CONFPATH environnement variable in your Windows settings
> >
> > This is not the intended use, it is only meant for people that wish to
> > override the build-in default value. Provide ./configure with the path
> > where the config files will be stored and most people will never have
> > to touch this.
> >
>
> Agree. But the question is : what is "the path where the config files
> will be stored" in a Windows environnement ? I am not sure how to handle
> this correctly right now. If you have any suggestion...
>

good point: I'm still unsure about the best solution here!
- we could keep the unix way, which is the path nut has followed for years,
by keeping config files. But the above question is still valid: where to put
these data (c:\etc or). In all case, this is a configure param.
- or we could have a more native windows approach, by having the conf stored
in the registry. Though this needs to change the *conf implementation.

In both cases, I don't know if there is a better solution for addressing at
the same time the security side of the config ...

Arno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20101020/8d7e437a/attachment.htm>